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
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 CENTOS
abrt-action-generate-core-backtrace
ABRT-ACTION-GENERA(1) ABRT Manual ABRT-ACTION-GENERA(1)NAME
abrt-action-generate-core-backtrace - Generates coredump-level backtrace
SYNOPSIS
abrt-action-generate-core-backtrace [-v] [-r] [-d DIR]
DESCRIPTION
This tool uses coredump from the file coredump and binary at the path stored in file executable in the problem directory to generate
coredump-level backtrace.
Coredump-level backtrace resembles ordinary backtrace in that it contains information about call frames present on the stack at the time of
the crash. However, it only contains information that can be obtained from the coredump without debugging symbols available - mainly
relative addresses of the stored instruction pointers. Such backtrace can still be useful for reporting and reproducing the bug and does
not require debugging information files to be installed.
The result is saved in the problem directory in a file named core_backtrace.
Integration with libreport events
abrt-action-generate-core-backtrace can be used as an analyzer for application crashes which dump core.
Example usage in report_event.conf:
EVENT=analyze analyzer=CCpp
abrt-action-generate-core-backtrace
OPTIONS -d DIR
Path to problem directory.
-r
Do not hash function fingerprints. Useful for debugging.
-v
Be more verbose. Can be given multiple times.
AUTHORS
o ABRT team
abrt 2.1.11 06/18/2014 ABRT-ACTION-GENERA(1)