[Mono-bugs] [Bug 472050] New: Debugger is unusable for Moonlight
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Tue Feb 3 12:59:08 EST 2009
https://bugzilla.novell.com/show_bug.cgi?id=472050
Summary: Debugger is unusable for Moonlight
Classification: Mono
Product: Mono: Debugger
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: backend
AssignedTo: martin at novell.com
ReportedBy: gnorton at novell.com
QAContact: mono-bugs at lists.ximian.com
Found By: ---
Attempting to start firefox in the debugger yields:
[2.14][12:55] plasma at limestone:~/tmp/debugger$ mdb /usr/lib64/firefox/firefox
-p moonlight -no-remote
Mono Debugger
(mdb) r
Starting program: /usr/lib64/firefox/firefox -p moonlight -no-remote
Failed to initialize thread_db on
/usr/lib64/firefox/firefox:-p:moonlight:-no-remote:
Mono.Debugger.Backend.ProcessStart
(/home/plasma/tmp/debugger:/usr/lib64/firefox/firefox:-p:moonlight:-no-remote:True)
at System.Environment.get_StackTrace() in
/home/plasma/src/mcs/class/corlib/System/Environment.cs:line 202
at
Mono.Debugger.Backend.ProcessServant.get_thread_info(Mono.Debugger.Backend.Inferior
inferior, Mono.Debugger.Backend.SingleSteppingEngine engine) in
/home/plasma/tmp/debugger/backend/ProcessServant.cs:line 470
at
Mono.Debugger.Backend.ProcessServant.ThreadCreated(Mono.Debugger.Backend.Inferior
inferior, Int32 pid, Boolean do_attach) in
/home/plasma/tmp/debugger/backend/ProcessServant.cs:line 197
at
Mono.Debugger.Backend.ThreadManager.HandleChildEvent(Mono.Debugger.Backend.SingleSteppingEngine
engine, Mono.Debugger.Backend.Inferior inferior,
Mono.Debugger.Backend.ChildEvent ByRef cevent, Boolean ByRef resume_target) in
/home/plasma/tmp/debugger/backend/ThreadManager.cs:line 170
at
Mono.Debugger.Backend.SingleSteppingEngine.ProcessEvent(Mono.Debugger.Backend.ChildEvent
cevent) in /home/plasma/tmp/debugger/backend/SingleSteppingEngine.cs:line 203
at Mono.Debugger.Backend.SingleSteppingEngine.ProcessEvent(Int32 status) in
/home/plasma/tmp/debugger/backend/SingleSteppingEngine.cs:line 152
at Mono.Debugger.Backend.ThreadManager.engine_thread_main() in
/home/plasma/tmp/debugger/backend/ThreadManager.cs:line 326
at Mono.Debugger.Backend.ThreadManager.start_inferior() in
/home/plasma/tmp/debugger/backend/ThreadManager.cs:line 97
EXCEPTION: Mono.Debugger.InternalError: Internal error.
at Mono.Debugger.Backend.ProcessServant.get_thread_info
(Mono.Debugger.Backend.Inferior inferior,
Mono.Debugger.Backend.SingleSteppingEngine engine) [0x000a8] in
/home/plasma/tmp/debugger/backend/ProcessServant.cs:470
at Mono.Debugger.Backend.ProcessServant.ThreadCreated
(Mono.Debugger.Backend.Inferior inferior, Int32 pid, Boolean do_attach)
[0x0008f] in /home/plasma/tmp/debugger/backend/ProcessServant.cs:197
at (wrapper remoting-invoke-with-check)
Mono.Debugger.Backend.ProcessServant:ThreadCreated
(Mono.Debugger.Backend.Inferior,int,bool)
at Mono.Debugger.Backend.ThreadManager.HandleChildEvent
(Mono.Debugger.Backend.SingleSteppingEngine engine,
Mono.Debugger.Backend.Inferior inferior, Mono.Debugger.Backend.ChildEvent&
cevent, System.Boolean& resume_target) [0x0002e] in
/home/plasma/tmp/debugger/backend/ThreadManager.cs:170
at (wrapper remoting-invoke-with-check)
Mono.Debugger.Backend.ThreadManager:HandleChildEvent
(Mono.Debugger.Backend.SingleSteppingEngine,Mono.Debugger.Backend.Inferior,Mono.Debugger.Backend.Inferior/ChildEvent&,bool&)
at Mono.Debugger.Backend.SingleSteppingEngine.ProcessEvent
(Mono.Debugger.Backend.ChildEvent cevent) [0x001e0] in
/home/plasma/tmp/debugger/backend/SingleSteppingEngine.cs:203
at Mono.Debugger.Backend.SingleSteppingEngine.ProcessEvent (Int32 status)
[0x0000c] in /home/plasma/tmp/debugger/backend/SingleSteppingEngine.cs:152
at (wrapper remoting-invoke-with-check)
Mono.Debugger.Backend.SingleSteppingEngine:ProcessEvent (int)
at Mono.Debugger.Backend.ThreadManager.engine_thread_main () [0x000cd] in
/home/plasma/tmp/debugger/backend/ThreadManager.cs:326
Trying to quit the debugger locks up the machine for about a minute until we
finally get:
(mdb) q
The program is running. Exit anyway? (y or n) y
GThread-ERROR **: file gthread-posix.c: line 261 (g_cond_free_posix_impl):
error 'Device or resource busy' during 'pthread_cond_destroy ((pthread_cond_t
*) cond)'
aborting...
Stacktrace:
at (wrapper managed-to-native)
Mono.Debugger.Backend.DebuggerEventQueue.mono_debugger_cond_free (intptr) <IL
0x0000f, 0x00056>
at (wrapper managed-to-native)
Mono.Debugger.Backend.DebuggerEventQueue.mono_debugger_cond_free (intptr) <IL
0x0000f, 0xffffffff>
at Mono.Debugger.Backend.DebuggerEventQueue.DoDispose () [0x00000] in
/home/plasma/tmp/debugger/backend/EventQueue.cs:170
at Mono.Debugger.Backend.DebuggerWaitHandle.Dispose (bool) [0x00018] in
/home/plasma/tmp/debugger/backend/EventQueue.cs:55
at Mono.Debugger.Backend.DebuggerWaitHandle.Finalize () [0x00000] in
/home/plasma/tmp/debugger/backend/EventQueue.cs:71
at (wrapper runtime-invoke) object.runtime_invoke_void__this__
(object,intptr,intptr,intptr) <IL 0x0004a, 0xffffffff>
Native stacktrace:
mono [0x484820]
/lib64/libpthread.so.0 [0x7f568fd7fa90]
/lib64/libc.so.6(gsignal+0x35) [0x7f568f7f4645]
/lib64/libc.so.6(abort+0x183) [0x7f568f7f5c33]
/usr/lib64/libglib-2.0.so.0(g_logv+0x4de) [0x7f56903de1de]
/usr/lib64/libglib-2.0.so.0(g_log+0x83) [0x7f56903de273]
/usr/lib64/libgthread-2.0.so.0 [0x7f5690661556]
/opt/mono/lib/libmonodebuggerserver.so(mono_debugger_cond_free+0x2a)
[0x7f568e022d5e]
[0x404ddd66]
Debug info from gdb:
/opt/mono/bin/mono (deleted): No such file or directory.
* 1 process 26426 0x8fd7f1b1 in ?? ()
Thread 1 (process 26426):
#0 0x8fd7f1b1 in ?? ()
=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
Aborted
At which point firefox finally launches.
--
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