[Issue 136] Corrupt GDB backtrace

[d-bugmail at puremagic.com]

http://d.puremagic.com/issues/show_bug.cgi?id=136


cristian at zerobugs.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yvad at mail.ru,
                   |                            |cristian at zerobugs.org




------- Comment #7 from cristian at zerobugs.org  2007-03-18 13:37 -------
Have tried with dmd 1.009 on a Fedora6 box. Zero shows the same behavior (line
4 shows up in the stack trace several times), and gdb (6.5-15.fc6rh) says:

(gdb) run
Starting program: /home/cristiv/dmd/bug 
[Thread debugging using libthread_db enabled]
[New Thread 1235648 (LWP 18592)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1235648 (LWP 18592)]
0x08049e46 in _Dmain () at bug.d:5
5               *(cast(int *)0) = 0;
Current language:  auto; currently minimal
(gdb) bt
#0  0x08049e46 in _Dmain () at bug.d:5
#1  0x00d316c8 in _r_debug ()
#2  0xbf865250 in ?? ()
#3  0x08049e40 in _Dmain () at bug.d:4
Previous frame inner to this frame (corrupt stack?)


--