any idea as to why following stack trace appears

Ramana Radhakrishnan
Wed Apr 28 15:49:00 GMT 2004


>following is the stack trace on doing "where" over a core for my app.
>this app has been working fine for as long as i know it, and all of
>sine last 2-3 days, it's been dumping core. 
>(gdb) where
>#0  0x00000673 in ?? ()
>#1  0x08048ac4 in strcpy () at strcpy:-1
>#2  0x4006f687 in __libc_start_main (main=0x8048a58 <strcpy+356>,
>    ubp_av=0xbffec794, init=0x804871c, fini=0x8086210 <__udivdi3+336>,
>    rtld_fini=0x4000dc54 <_dl_fini>, stack_end=0xbffec78c)
>    at ../sysdeps/generic/libc-start.c:129

Minimum :

Information regarding the platform, the compiler , libc version used, 
gdb version used would be useful for anyone to make a start .If possible 
a complete script of the session where you had such a problem would 
definitely be a good starting point (man script)

Bonus :
A small testcase showing a similar scenario would help.


More information about the Gdb mailing list