RE: Executable with non-debugging info.

[Hiro Sugawara <hsugawar at brocade dot com>]

It may depend on the operating system, but the information obtained from a
core file does not usually depend on whether the executable has debug
information. I your particular case, however, I doubt if the information
is correct because "signal 9" is SIGKILL and it is not supposed to produce
a core file. SIGKILL is supposed to terminate the process immediately.

hiro

> -----Original Message-----
> From: Jagat Patel [mailto:patelj@nortelnetworks.com]
> Sent: Thursday, July 05, 2001 08:19
> To: gdb@sourceware.cygnus.com
> Subject: Executable with non-debugging info.
> 
> 
> > Hi,
> >
> > I have executable (from c++ source) that was created 
> without debugging
> information
> > ( without -g option while compiling ). While running it, there was
> core
> > dump. I started gdb with following command:
> >
> > gdb <exe filename> core
> 
> > I got following two information from gdb:
> >
> > gbd message indicate that the program was terminated using signal 9.
> > "info stack" command at gdb prompt give me the stack trace ( in some
> > encripted form but still I can make out the function calls )
> >
> > My question is are the above two information reliable. I am asking
> this
> > because my executable was NOT having debugging information.
> >
> > Thank you,
> > Jagat
> >
> 
>