CDT Managed Build UI crash- how to debug? [message #165825] |
Tue, 14 March 2006 12:51  |
Eclipse User |
|
|
|
Originally posted by: jamesm.filmlight.ltd.uk
I'm experiencing the following crash when trying to access the C++
Builder UI in the Properties window for my C++ Managed Make project.
I'm using Eclipse 3.1.2 with CDT 3.0.2. Admittedly, I'm running on
Redhat 9 with GTK 2.2.
I was wondering how best you would go about debugging this code? Fire up
GDB and attach to the process?
If there is a web page outlining how best to debug this mixed-mode code,
please feel free to point me at it :-)
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xb123e74d, pid=13280, tid=3085969472
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_06-b05 mixed mode, sharing)
# Problematic frame:
# C [libgtk-x11-2.0.so.0+0x19b74d]
#
--------------- T H R E A D ---------------
Current thread (0x0805cac8): JavaThread "main" [_thread_in_native,
id=13280]
siginfo:si_signo=11, si_errno=0, si_code=1, si_addr=0x00000008
Registers:
EAX=0x00000000, EBX=0xb12f18b8, ECX=0x00000000, EDX=0x08723f00
ESP=0xbf942dc8, EBP=0xbf942eb0, ESI=0x08726e18, EDI=0x000000bb
EIP=0xb123e74d, CR2=0x00000008, EFLAGS=0x00010246
Top of Stack: (sp=0xbf942dc8)
0xbf942dc8: 0881aa70 bf942e88 08883928 bf942e64
0xbf942dd8: b0fa6500 08426e14 00000000 b12f18b8
0xbf942de8: b12f18b8 00000000 bf942e80 b1264ddb
0xbf942df8: 08723f00 00000001 bf942e88 00000000
0xbf942e08: bf942e4c bf942e4c bf942e40 b78e2e1f
0xbf942e18: b78e2e30 bf942e28 08426e78 08237828
0xbf942e28: bf942f94 00000000 08726e18 00000000
0xbf942e38: 00000000 00000000 00000000 00000000
Instructions: (pc=0xb123e74d)
0xb123e73d: 00 00 00 e9 31 f6 ff ff 8b 55 80 8b 4a 20 eb a4
0xb123e74d: 8b 41 08 8b 51 04 8b 76 20 8b 40 14 89 85 74 ff
Stack: [0xbf748000,0xbf948000), sp=0xbf942dc8, free space=2027k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code,
C=native code)
C [libgtk-x11-2.0.so.0+0x19b74d]
C [libgtk-x11-2.0.so.0+0x1990e2]
C [libgtk-x11-2.0.so.0+0xd5c2f] _gtk_marshal_BOOLEAN__BOXED+0x5f
C [libgobject-2.0.so.0+0x9247]
C [libgobject-2.0.so.0+0x8ed7] g_closure_invoke+0xb7
C [libgobject-2.0.so.0+0x1b439]
C [libgobject-2.0.so.0+0x1a7af] g_signal_emit_valist+0x47f
C [libgobject-2.0.so.0+0x1abe4] g_signal_emit+0x34
C [libgtk-x11-2.0.so.0+0x1bb6fb]
C [libgtk-x11-2.0.so.0+0xd46fc] gtk_main_do_event+0x1dc
C [libswt-pi-gtk-3139.so+0x2f4fc]
Java_org_eclipse_swt_internal_gtk_OS__1gtk_1main_1do_1event+ 0x1b
J org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(I)V
J org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(I)V
J org.eclipse.swt.widgets.Display.eventProc(II)I
v ~StubRoutines::call_stub
V [libjvm.so+0x174fec]
V [libjvm.so+0x2821f8]
V [libjvm.so+0x174e1f]
V [libjvm.so+0x19f873]
V [libjvm.so+0x183b8e]
C [libswt-gtk-3139.so+0x24fac] callback+0x1e4
C [libswt-gtk-3139.so+0x12cc6] fn2_2+0x20
C [libgdk-x11-2.0.so.0+0x2edb5]
C [libgdk-x11-2.0.so.0+0x2ef88] gdk_window_process_updates+0x88
C [libgtk-x11-2.0.so.0+0x19fae2]
C [libgtk-x11-2.0.so.0+0x1a5e9b]
C [libgtk-x11-2.0.so.0+0x1a6158] gtk_tree_view_set_cursor_on_cell+0xe8
C [libgtk-x11-2.0.so.0+0x1a605c] gtk_tree_view_set_cursor+0x3c
C [libswt-pi-gtk-3139.so+0x32c3b]
[blah blah- shan't bore you with the rest]
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05916 seconds