[Mono-bugs] [Bug 423518] WARNING: Got event 137f for unknown pid xxxx

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Thu Jan 8 22:22:07 EST 2009


User mike at trausch.us added comment

--- Comment #49 from Michael Trausch <mike at trausch.us>  2009-01-08 20:22:04 MST ---
Okay, so...

Something has changed, but I have *no clue* what.  Now, every single time I
attempt to use mdb to debug an application, it results in a SIGSEGV, and it
doesn't matter if it is 2.6.26 or 2.6.27 or 2.6.28.  I have tried using older
SVN revisions of the Mono Debugger that I was using earlier when I ran into
this bug report, which failed causing the same issues.  I am going to post what
I am running into here, just in the event that a light bulb might go off in
somebody's head and tell me what kind of idiocy I have likely committed
somewhere (source for hello.exe below):

test> mdb hello.exe
Mono Debugger
(mdb) run
Starting program: hello.exe 
Thread @1 received signal 11 at #0: 0x7fff68c60910.
0x7fff68c60910  int3   
(mdb) cont

Native stacktrace:

        /usr/home/mbt/opt/mono-2.0/bin/mono [0x429e55]
        /usr/home/mbt/opt/mono-2.0/bin/mono [0x44ba7d]
        /lib/libpthread.so.0 [0x7f415ff600f0]

Debug info from gdb:

ptrace: Operation not permitted.
No registers.
No registers.

Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.

Thread @1 received signal 6 at #0: 0x7f415f98cfd5 in raise+0x35.
0x7f415f98cfd5  cmp    $0xfffffffffffff000,%rax
(mdb) cont
Thread @1 died with fatal signal 6.
(mdb) Thread @1 exited.
Process #1 exited.
Target exited.

---- hello.cs source code ----
using System;

public static class EntryPoint {
  public static int Main(string[] args) {
    string target;

    if(args.Length == 0) {
      target = "World";
    } else {
      target = args[0];

    Console.WriteLine("Hello, {0}!", target);

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the mono-bugs mailing list