[Issue 136] Corrupt GDB backtrace
d-bugmail at puremagic.com
d-bugmail at puremagic.com
Fri Mar 2 04:29:43 PST 2007
http://d.puremagic.com/issues/show_bug.cgi?id=136
------- Comment #6 from thomas-dloop at kuehne.cn 2007-03-02 06:29 -------
This is defiantly a DMD issue. DMD-0.157 produces a .debug_frame section
whereas DMD-0.155 doesn't. If the .debug_frame section is removed GDB displays
the correct trace.
dmd-0.157 -c -g a.d && objcopy -R .debug_frame a.o b.o && dmd-0.157 b.o -ofb &&
gdb ./b
(gdb) run
Starting program: /tmp/b
[Thread debugging using libthread_db enabled]
[New Thread 4157970096 (LWP 113)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 4157970096 (LWP 113)]
0x0804a09a in _Dmain () at a.d:5
5 *(cast(int *)0) = 0;
Current language: auto; currently minimal
(gdb) bt
#0 0x0804a09a in _Dmain () at a.d:5
#1 0x0804a094 in _Dmain () at a.d:4
#2 0x0804a094 in _Dmain () at a.d:4
#3 0x0804a094 in _Dmain () at a.d:4
#4 0x0804a094 in _Dmain () at a.d:4
#5 0x0804a094 in _Dmain () at a.d:4
#6 0x0804a094 in _Dmain () at a.d:4
#7 0x0804a094 in _Dmain () at a.d:4
#8 0x0804a094 in _Dmain () at a.d:4
#9 0x0804a094 in _Dmain () at a.d:4
#10 0x0804a094 in _Dmain () at a.d:4
#11 0x0804a163 in main ()
--
More information about the Digitalmars-d-bugs
mailing list