Hi,
This looks ok to me. I will try to test it on sparc/solaris, then
check it in, if it works.
Zoltan
On 3/25/06, David S. Miller [EMAIL PROTECTED] wrote:
From: David S. Miller [EMAIL PROTECTED]
Date: Fri, 24 Mar 2006
From: Zoltan Varga [EMAIL PROTECTED]
Date: Sat, 25 Mar 2006 12:30:23 +0100
This looks ok to me. I will try to test it on sparc/solaris, then
check it in, if it works.
Thanks a lot Zoltan.
___
Mono-devel-list mailing list
Hi,
I've done some playing around running some of our mono programs on Solaris
(i386) and the default behaviour for SIGSEV in native code appears to be to
generate a core dump. For example if I try and bind to TCP port 80 on Solaris I
get a core dump whereas on Windows and Linux I can catch the
SIGSEGV are not converted to exceptions in recent mono 1.1 releases, not even
on linux and windows. What mono version are you using ? The default
behavior is to abort after printing some diagnostic messages, and this
cannot be changed.
Also, binding to a reserved port shouldn't cause a SIGSEGV.
Hi,
I forgot to say it was attempting to bind to the reserved port on a separate
thread. If the bind is attempted on the main thread then the exception is caught
ok.
This code throws a SIGSEGV on Solaris for me.
In main:
IPAddress m_testIPAddress =
Hi,
I couldn't repro this, it prints 'Access Denied' for me on sparc/x86. Please
attach a complete testcase.
Zoltan
On 3/25/06, Aaron Clauson [EMAIL PROTECTED] wrote:
Hi,
I forgot to say it was attempting to bind to the
Hi,
Why is there no 2.0 profile version of all Mono tools (such as resgen, xsd,
...) ?
Right now, it's not possible to use any of these tools when you want to
build 2.0 applications.
If you have, for example, a resx file for which you need to reference a 2.0
assembly, then it's not possible to
Jonathan Pryor wrote
On Fri, 2006-03-24 at 16:02 +0100, Jakub Cermak wrote:
Deleting this shared data can have bad effects on mono applications. :-)
- Jon
Wapi data (at /root/.wapi/) hasn't been deleted - last modifed time of
these files is time of Mono instalation :(
--
Jakub Cermak
Jakub Cermak wrote:
Jonathan Pryor wrote
On Fri, 2006-03-24 at 16:02 +0100, Jakub Cermak wrote:
Deleting this shared data can have bad effects on mono applications. :-)
- Jon
Wapi data (at /root/.wapi/) hasn't been deleted - last modifed time of
these files is time of Mono instalation
Hi Zoltan,
You are right, sorry about that.
It actually turns out this is the line producing the SIGSEGV on Solaris x86:
IPAddress testAddress = null;
Console.WriteLine(Test Address = + testAddress.ToString());
It will be easy to work around now I've worked out what the proper cause is but
Hey,
This is because resgen is a 1.1 (1.0 profile) assembly (which loads some 1.1
system assemblies) and hence you end with a 1.0 runtime, which ofcourse
can't deal with 2.0 assemblies.
Why not just build all Mono tools in both 1.0 and 2.0 profile ? Even if the
source code is exactly the
minfo-lexical_blocks is a raw pointer into the symbol table metadata
information of a *.dll file. Therefore it may be aligned arbitrarily,
and it's in little-endian format.
Therefore the entry members must be accessed using the read*()
interfaces.
I guess --debug is untested on both UNALIGNED
I developed a mono program in Linux, which can be found here:
http://fileuniverse.com/?p=showitemID=2746
It all works fine in my Widows and Linux boxes.
But my (Windows only) users are not beeing able to run it. Here is the error
message:
### Message ###
D:\DOCUME~1\mike\Desktop\EdSv0.9mono
Forgot to mention, i am using mono 1.1.13. And my users should be using the same
because they installed mono specifically for using my program.
Citando [EMAIL PROTECTED]:
I developed a mono program in Linux, which can be found here:
http://fileuniverse.com/?p=showitemID=2746
It all works
14 matches
Mail list logo