The simple way to get a core that "starts" at the fault is not to block signals. Obviously this has some very bad downsides.
Otherwise with what you have done you have to traverse stack frames back to the problem, in gdb this is the
Code:
backtrace
command. Signal receipt when blocked causes an immediate interrupt to the executing code, pushing the state of the process and kernel onto the interrupt stack. Working backwards can be fun.
Some example code for gaddr2line():
Note that you should consider libelf instead of the python library.
I am using dbx for debugging core and the corresponding command for backtrace is where in dbx. But as I said earlier I am getting the stack of signal handler routine through backtrace and not the location of faulty code.
Hi,
Is there anything you can do to a *nix (SuSE Linux actually) which allows it to *try* to do a reboot if something crashes the system?
I know they have something at work (but I don't work with the servers myself) which makes the server reboot if it crashes/locks (works about 80% of the... (0 Replies)
Hi there,
I found a link to a file /dev/core of 17 GB
Is it ok??? I couldn't find many information about it.
Any suggestion would be appreciated!!!
Thanks in advance,
Giordano Bruno
PS: I'm working with FEDORA 6 (2 Replies)
Hi All,
I have scenario where my callback function data_update() can be called anytime. I have written the function data_update() such that it will create detached thread for processing the data sent to this function.
data_update()
{
pthread_attr_t attr_thread;
... (1 Reply)
I´m writing this program in QNX , I`m kinda new to UNIX and programing in general, and when I try to run it it gives me the Memory Fault error. Can anyone help?
#include <stdio.h>
#include <fcntl.h>
void main(void)
{int a,ter;
char buf;
printf("a=");
scanf("%d",a);
ter=open... (6 Replies)
in a single main() function,so need signal handling. Use Posix Message Queue IPC mechanism , can ignore the priority and other linked list message,to implement the scenario:
client:Knock Knock
server:who's there
client: Eric
Server:Eric,Welcome.
client:exit
all process terminated
... (1 Reply)
Greetings,
I am writing a small program in C on UNIX, in which I am using (POSIX reliable) signals.
1. Suppose I have a signal : SIGX, and the corresponding signal handler : sigx_handler.
It is possible to receive SIGX in my process, and, while executing sigx_handler, to receive
again... (0 Replies)
I am in process of writing a library which can make any application of my product capable of creating core in the application's log folder with a product friendly core file name programatically. In my library I am registering for certain signals e.g. SIGILL, SIGFPE, SIGBUS, SIGSEGV, SIGSYS, SIGABRT... (1 Reply)
What will happen if signal comes while a system call is being executed?
How it will be handled? (1 Reply)
Discussion started by: rupeshkp728
1 Replies
LEARN ABOUT HPUX
gcore
gcore(1) General Commands Manual gcore(1)NAME
gcore - get core images of running processes
SYNOPSIS
filename] process-id...
DESCRIPTION
The command creates a core image of each specified process. By default, the name of the core image file for process-id will be The process
information in the core file can be obtained by using debuggers.
When the command creates a core image of each specified process, the process is temporarily stopped. Further, when the creation of core
image is complete, the process continues to execute.
Options
Creates the core file with name of the file as
If multiple process-id values are specified, filename will be common for all the core image files. See the section.
Operands
process-id The process ID for which a core image file will be created.
RETURN VALUE
Upon completion, exits with one of the following values:
A core file was successfully created.
An error condition was encountered.
In such a case, the creation of a core file is not guaranteed. The error conditions could be because of
o A nonexistent or incorrect process ID was specified.
o An invalid option was specified.
o The current working directory of the process or directory from which was invoked had no write permissions.
o The current working directory of the process was not accessible.
o The file system is full.
EXAMPLES
Example 1
Dump the core image of process 1030 in the file "core.1030".
Example 2
Dump the core image of the process 1030 in the file "test.1030".
Example 3
Dump the core image of the processes 1030, 1031, 1032, and 1033 in the files "core.1030", "core.1031", "core.1032", "core.1033".
Example 4
Dump the core image of the processes 1030, 1031, 1032, and 1033 in the files
FILES
Core image file for process-id. (Both where is invoked and the current working directory of the process.)
AUTHOR
was developed by Chris Bertin (HP).
SEE ALSO adb(1), gdb(1), kill(1), ttrace(2), a.out(4), core(4).
gcore(1)