12-05-2012
Bumping up posts or double posting is not permitted in these forums.
Please read the
rules, which you agreed to when you registered, if you have not already done so.
You may receive an infraction for this. If so, don't worry, just try to follow the rules more carefully. The infraction will expire in the near future
Thank You.
The UNIX and Linux Forums.
10 More Discussions You Might Find Interesting
1. Programming
Hi,
i cannot find in which file and function the signals are handled by
default.Can anyone help me?
How can i create a 33th signal?
Thanks (3 Replies)
Discussion started by: Panos
3 Replies
2. UNIX for Dummies Questions & Answers
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)
Discussion started by: d11wtq
0 Replies
3. Shell Programming and Scripting
Hi,
Iam having the file as follows:
QWASEDRF1234567890098765 abc@quebex.com 000000000-932333 678394-56=3 9033894
QWASEDRF1234567890098765 abc@quebex.com 000000000-932333 678394-56=3 9033894
OPIUYTREE0986666544443322 dcsx@olivaa.net ... (14 Replies)
Discussion started by: nivas
14 Replies
4. Filesystems, Disks and Memory
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)
Discussion started by: Giordano Bruno
2 Replies
5. Programming
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)
Discussion started by: wonderman
1 Replies
6. Programming
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)
Discussion started by: GiganteAsesino
6 Replies
7. Programming
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)
Discussion started by: ouou
1 Replies
8. UNIX for Dummies Questions & Answers
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)
Discussion started by: aigoia
0 Replies
9. Solaris
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... (5 Replies)
Discussion started by: rajeev_ks
5 Replies
10. UNIX for Advanced & Expert Users
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
gcore(1) BSD General Commands Manual gcore(1)
NAME
gcore -- get core images of running processes
SYNOPSIS
gcore [-s] [-v] [-b size] [-o path | -c pathformat] pid
DESCRIPTION
The gcore program creates a core file image of the process specified by pid. The resulting core file can be used with a debugger, e.g.
lldb(1), to examine the state of the process.
The following options are available:
-s Suspend the process while the core file is captured.
-v Report progress on the dump as it proceeds.
-b size Limit the size of the core file to size MiBytes.
The following options control the name of the core file:
-o path
Write the core file to path.
-c pathformat
Write the core file to pathformat. The pathformat string is treated as a pathname that may contain various special characters which
cause the interpolation of strings representing specific attributes of the process into the name.
Each special character is introduced by the % character. The format characters and their meanings are:
N The name of the program being dumped, as reported by ps(1).
U The uid of the process being dumped, converted to a string.
P The pid of the process being dumped, converted to a string.
T The time when the core file was taken, converted to ISO 8601 format.
% Output a percent character.
The default file name used by gcore is %N-%P-%T. By default, the core file will be written to a directory whose name is determined from the
kern.corefile MIB. This can be printed or modified using sysctl(8).
The directory where the core file is to be written must be accessible to the owner of the target process.
gcore will not overwrite an existing file, nor will it create missing directories in the path.
EXIT_STATUS
The gcore utility exits 0 on success, and >0 if an error occurs.
FILES
/cores/%N-%P-%T default pathname for the corefile.
BUGS
With the -b flag, gcore writes out as much data as it can up to the specified limit, even if that results in an incomplete core image. Such
a partial core dump may confuse subsequent programs that attempt to parse the contents of such files.
SEE ALSO
lldb(1), core(5), Mach-O(5), sysctl(8), sudo(8).
Darwin May 31, 2019 Darwin