05-08-2008
The problem is only happening in Prod. Tracing is out of the question.
I did the following:
$ ulimit -c 9999999999 ## set core file size to unlimited
$ kill -s SIGSEGV <PID> ## Is this how a signal is sent to a PID??
The process terminates and no core files are created.
Is it required that the application has to be built/coded specifically to accept signals?
TIA.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
2. UNIX for Dummies Questions & Answers
does any one have read a core dump?
is there any reader for that? or may i know what is the use of that core which takes sometimes memory in GBs?
:) (6 Replies)
Discussion started by: sskb
6 Replies
3. UNIX for Dummies Questions & Answers
I've got a core dump in my weblogic home directory, which i have tried to debug by initiating savecore from /etc/init.d/savecore start
but savecore failed to create the two files, that is vmcore.n and vmunix.n.
savecore is enable on my server to save vmcore and vmunix in /var/crash/hostname
1)... (4 Replies)
Discussion started by: hassan2
4 Replies
4. UNIX for Advanced & Expert Users
Hi All,
i am new to this forum.i want detail of reading the core file and trace the problem because of what the program get crashed.please help me.if any body knows any website or tutoril plese let me know.
sudhir (6 Replies)
Discussion started by: sudhir patnaik
6 Replies
5. AIX
My application gives core dump. When i am debugging with dbx getting instructions below:
pthdb_session.c, 818: 695445 PTHDB_INTERNAL (internal error)
pthreaded.c, 1941: PTHDB_INTERNAL (internal error)
Illegal instruction (illegal opcode) in . at 0x0
warning: Unable to access address 0x0... (1 Reply)
Discussion started by: bapi
1 Replies
6. AIX
Hi ,
I want to read core dump file on AIX5.3. While i am trying to use following commands, i am getting only few lines of information.
ux201p3:e46123> dbx capsWrkstnMgr core
Type 'help' for help.
reading symbolic information ...
Segmentation fault in malloc_common.extend_brk at... (1 Reply)
Discussion started by: rps
1 Replies
7. Red Hat
Hello
Im using redhat and try to debug my application , its crashes and in strace I also see it has problems , but I can't see any core dump
I configured all the limit ( im using .cshrc ) and it looks like this :
cputime unlimited
filesize unlimited
datasize unlimited... (8 Replies)
Discussion started by: umen
8 Replies
8. HP-UX
Hi Guys,
I was wondering if somebody could give me a link to a very good source of information or document about core dump process and How to's about it. I have also googled it and found some articles myself.
Thanks
Messi (1 Reply)
Discussion started by: messi777
1 Replies
9. Solaris
Hi guys,
just want to know which core file pattern is best to set for core dumps:
1) per-process file name pattern
or
2) global file name pattern.
I will really appreciate an explanation why the chosen one is better.
Thanks a lot guys. (2 Replies)
Discussion started by: cjashu
2 Replies
10. Red Hat
Hello All,
I am new joiner of this forum.I am new to Linux shell scripting.
At present I have identified 1 application which stalls very frequently (PID is say xyz) and I am not having much information in its application log to identify the root cause of stalling. I need to take the core dump... (19 Replies)
Discussion started by: Anjan Ganguly
19 Replies
abort(3C) abort(3C)
NAME
abort() - generate a software abort fault
SYNOPSIS
DESCRIPTION
first closes all open files, streams, directory streams, and message catalogue descriptors, if possible, then causes the signal to be sent
to the calling process. This may cause a core dump to be generated (see signal(2)).
If the signal is caught, the handling function is executed. If the handling function returns, the action for is then reset to and the sig-
nal is sent again to the process to ensure that it terminates.
RETURN VALUE
does not return.
ERRORS
No errors are defined.
APPLICATION USAGE
is not intended to be caught.
DIAGNOSTICS
If is neither caught nor ignored, and the current directory is writable, a core dump is produced and the message is written by the shell.
SEE ALSO
adb(1), exit(2), kill(2), signal(2), signal(5), thread_safety(5).
STANDARDS CONFORMANCE
abort(3C)