Hi,
I'm trying to build mono-debugger 0.60 on my F9 box (running on rawhide,
but that's not really anything new and everything normally just builds).
Besides a small patch needed to build the server on the backend
(attached) I seem to be hitting a problem just building it.
Is there a fix in the
doing nothing. Hope I am clear this time. Looking at the stack trace
I _think_ its just some bug in mono's after-crash-stacktrace-printer
which is causing the problem. Mono's behaviour (and yours too) is
absolutely right otherwise.
It's most likely the g_spawn* that gets the stack
Dick, do you have any input on this before I start implementing the
Win32 Comm API in io-layer?
On Apr 21, 2008, at 5:53 AM, Geoff Norton wrote:
Josh,
At a high level it does, but this conversation should be moved over
to mono-devel-list, so that the approrpiate maintainers (Dick
Paramesh,
The following link is what I use. I have found it extremely useful.
http://shana.iidbbs.com/en/mono_cygwin_tutorial.html
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
Hi,
Now I redesigned several things but still fails to compile:
/mono/mono/mono/metadata/domain.c:1216: undefined reference to
[EMAIL PROTECTED]'
/mono/mono/mono/metadata/domain.c:1171: undefined reference to
[EMAIL PROTECTED]'
If I add this to domain.c it compiles just fine:
#include
Hi Kornél,
Kornél Pál wrote:
Now I redesigned several things but still fails to compile:
/mono/mono/mono/metadata/domain.c:1216: undefined reference to
[EMAIL PROTECTED]'
/mono/mono/mono/metadata/domain.c:1171: undefined reference to
[EMAIL PROTECTED]'
If I add this to domain.c it
In code I have to port from MS .NET to mono I observed several SIGILL
crashes at points in code, where calls to external code are made
within a try block followed by a finally but *without* a catch
statement.
try {
unrar.dosomething();
