Skip to contentSkip to conversation

Determining if process is having core dump

DISCUSSION Nirendra Awasthi 1 participant 2 messages Jun 7, 2004 Memory management

lore
Share & tools
lore
#0 lore raw

Hi,
Is there a way for a unrelated process to determine if another process
is exiting and is in the state of having core dump.

In solaris, this can be determined using libkvm(checking process flags
for SDOCORE and COREDUMP). Is there a way to do this in linux 2.6

One of the things I observed is flag in /proc/<pid>/stat (9th
attribute) is set to non-zero after process receives a signal to quit after core dump (SIGABRT, SIGQUIT etc.). Is it an indication that process is going to exit or what does it indicates.

Is there some other way to determine this. I don't want to limit size
of core file to 0 using ulimit, as this file is required to be analyzed later.
Also, while process is exiting and it receives another signal, it is
corrupting the core dump.

-Nirendra

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>

#1 lore raw

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 ?? ()

-Nirendra

Quoted 10 lines · Nirendra Awasthi

Hi,
Is there a way for a unrelated process to determine if another
process is exiting and is in the state of having core dump.

In solaris, this can be determined using libkvm(checking process
flags for SDOCORE and COREDUMP). Is there a way to do this in linux 2.6

One of the things I observed is flag in /proc/<pid>/stat (9th
attribute) is set to non-zero after process receives a signal to quit after core dump (SIGABRT, SIGQUIT etc.). Is it an indication that process is going to exit or what does it indicates.

Quoted 13 lines

Is there some other way to determine this. I don't want to limit
size of core file to 0 using ulimit, as this file is required to be analyzed later.
Also, while process is exiting and it receives another signal, it is
corrupting the core dump.

-Nirendra

Signature · 4 lines
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to [email protected].  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>