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.
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 OSF1
crashdc
crashdc(8) System Manager's Manual crashdc(8)NAME
crashdc - Diagnostic data collection for a running or crashed system
SYNOPSIS
/usr/bin/crashdc [system-kernel] [core-image]
DESCRIPTION
The crashdc utility examines the core image of the operating system to extract critical diagnostic data. This utility is a shell script
that invokes several tools and commands that extract selected parameters of a running or a crashed system (for example, system configura-
tion, running processes, and panic messages).
The arguments to the crashdc utility are the system kernel and the core image. The default values are /vmunix and /dev/mem, respectively.
If you specify no arguments, the crashdc utility examines the running system.
The system usually invokes the crashdc utility during system startup. If the most recent core dump has been saved by the savecore command,
both the core image and the system kernel (respectively vmcore.n and vmunix.n, where the variable n is the crash number) are saved in the
crash directory (by default, /var/adm/crash). Also, the crashdc utility saves the output as the file crash-data.n (where the variable n is
the crash number) in the crash directory. The crashdc utility is invoked only if crash-data.n output in the crash directory does not exist
or is not from the most recent crash.
FILES
Default core image Default system image Output from crashdc
SEE ALSO
Commands: dbx(1), kdbx(8), savecore(8)crashdc(8)