1820733 Members
3201 Online
109627 Solutions
New Discussion

Coredump with bad stack

 
chocard
Occasional Visitor

Coredump with bad stack

Hello,

My program crash on my hp-ux 11.11 and the coredump is not exploitable while I have the symbol.

I execute the gdb on the server where the application crash.

Can you tell me why my coredump is like this ?

>gdb -o test.debug -e test -c core
GNU gdb (GDB) 7.6.2
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "hppa2.0w-hp-hpux11.11".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /opt/MyApp/Server/bin/test.debug...done.
[New process 2516497]
[New process 2516618]
[New process 2516619]
[New process 2516620]
[New process 2516621]
[New process 2516622]
[New process 2516623]
[New process 2516624]
[New process 2516625]
[New process 2516627]
[New process 2516687]
[New process 2516688]
[New process 2516692]
[New process 2516693]
[New process 2516696]
(gdb) thread 1
[Switching to thread 1 (process 2516497)]
#0  0xc020deb0 in ?? ()
(gdb) where
#0  0xc020deb0 in ?? ()
#1  0xc0218cd4 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) thread 2
[Switching to thread 2 (process 2516618)]
#0  0xc020c878 in ?? ()
(gdb) where
#0  0xc020c878 in ?? ()
#1  0xc00593f8 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) thread 3
[Switching to thread 3 (process 2516619)]
#0  0xc020c878 in ?? ()
(gdb) where
#0  0xc020c878 in ?? ()
#1  0xc00593f8 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) thread 4
[Switching to thread 4 (process 2516620)]
#0  0xc020c878 in ?? ()
(gdb) where
#0  0xc020c878 in ?? ()
#1  0xc00593f8 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) thread 5
[Switching to thread 5 (process 2516621)]
#0  0xc020c878 in ?? ()
(gdb) where
#0  0xc020c878 in ?? ()
#1  0xc00593f8 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) thread 6
[Switching to thread 6 (process 2516622)]
#0  0xc020c878 in ?? ()
(gdb) where
#0  0xc020c878 in ?? ()
#1  0xc00593f8 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) thread 7
[Switching to thread 7 (process 2516623)]
#0  0xc020c878 in ?? ()
(gdb) where
#0  0xc020c878 in ?? ()
#1  0xc00593f8 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) thread 8
[Switching to thread 8 (process 2516624)]
#0  0xc020e8d0 in ?? ()
(gdb) where
#0  0xc020e8d0 in ?? ()
#1  0xc021a95c in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) thread 9
[Switching to thread 9 (process 2516625)]
#0  0xc020c878 in ?? ()
(gdb) we here
#0  0xc020c878 in ?? ()
#1  0xc00593f8 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) thread 10
[Switching to thread 10 (process 2516627)]
#0  0xc020c878 in ?? ()
(gdb) where
#0  0xc020c878 in ?? ()
#1  0xc00593f8 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) thread 11
[Switching to thread 11 (process 2516687)]
#0  0xc020e270 in ?? ()
(gdb) where
#0  0xc020e270 in ?? ()
#1  0xc0219ae8 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) thread 12
[Switching to thread 12 (process 2516688)]
#0  0xc020e270 in ?? ()
(gdb) where
#0  0xc020e270 in ?? ()
#1  0xc0219ae8 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) ther  read 13
[Switching to thread 13 (process 2516692)]
#0  0xc020e270 in ?? ()
(gdb) where
#0  0xc020e270 in ?? ()
#1  0xc0219ae8 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) tjrea    he read 14
[Switching to thread 14 (process 2516693)]
#0  0xc020c878 in ?? ()
(gdb) we here
#0  0xc020c878 in ?? ()
#1  0xc00593f8 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) thread 15
[Switching to thread 15 (process 2516696)]
#0  0xc0162738 in ?? ()
(gdb) where
#0  0xc0162738 in ?? ()
#1  0x00000000 in ?? ()
(gdb) thread 16
(gdb) quit

Thanks

1 REPLY 1
Dennis Handly
Acclaimed Contributor

Re: Coredump with bad stack

> Can you tell me why my coredump is like this?

 

Has the corefile been truncated?

Have you tried HP-UX's version of gdb?