Re: [LIP] Determining whether a process is exiting

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 

Hi,
	Is there a way for a unrelated process to determine if another process is
exiting and is in the process of 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

	flag in /proc/<pid>/stat (9th attribute) is set to non-zero after process
receives a signal. 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 may be analyzed later.

-Nirendra

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.



-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504