Re: Determining if a process is having core dump

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jun 07, 2004 at 17:52:02 +0530, Nirendra Awasthi wrote:
> Another problem I noticed is, while sending SIBABRT (or any signal which 
> causes core dump) to process already having core dump results in 
> corrupting core.
> 
> Following is the output while analyzing core with gdb:
> 
> Reading symbols from /lib/tls/libc.so.6...done.
> Loaded symbols for /lib/tls/libc.so.6
> Reading symbols from /lib/ld-linux.so.2...done.
> Loaded symbols for /lib/ld-linux.so.2
> #0  0xffffe411 in ?? ()

Is the program compiled with debugging and unstripped? It really looks
like the program is stripped.

-------------------------------------------------------------------------------
						 Jan 'Bulb' Hudec <bulb@ucw.cz>

Attachment: signature.asc
Description: Digital signature


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux