10-24-2009
While I can't understand why someone would want to run a program that generates a SIGBUS, you might try running it with strace or truss (depending on what system you are using. You will get more of information on what it was writing before the SIGBUS.
BTW, SIGBUS means the program trying to access something using an address reference that is not compatible with the object. That means something has really screwed up and could cause really bad things to happen to your data....
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
Hi ,
Working on AIX 4.3. An internal error from my apps engine suddenly causes the engine to die. During this time i do notice a core file being dumped in the directory from where I try to re-start my engine.
Q is how does one read this core file, or I should say 'what is this core file'?
thnx (2 Replies)
Discussion started by: buRst
2 Replies
3. UNIX for Advanced & Expert Users
I faced following problem while restoring root backup
Server : Compaq Proliant 6000
OS SCO : Unixware 7.0
#tar - xvf /dev/rmt/ctape1
After extracting some files following error message occurred and process stopped
# BUS ERROR CORE DUMPED
What may be the problem? How to avoid... (1 Reply)
Discussion started by: j1yant
1 Replies
4. Programming
how to view core dumped file using gdb and how to extract information from the coredumped file.can we get similar information from the other utilites like strace or ptrace. (2 Replies)
Discussion started by: Manabhanjan
2 Replies
5. Shell Programming and Scripting
Hi all,
I have a folder with some 28 files. I have a script file that will iteratively take one file at a time from the folder and provide an output for the input file. Till the 7th file, there was no problem but from the 8th file onwards, i got this Segmentation Fault(Core Dump) error. A file... (2 Replies)
Discussion started by: mick_000
2 Replies
6. UNIX for Dummies Questions & Answers
my progrme complaints 'Segmentation fault'.
How to let it print 'Segmentation fault(core dumped)' and generate core dump file?
$ulimit
unlimited (22 Replies)
Discussion started by: vistastar
22 Replies
7. Solaris
****** (0 Replies)
Discussion started by: meghnasreddy
0 Replies
8. Programming
HI,
I am getting run time error when am trying to compile the following coe can any one please help me
while (fgets(strLine, MAX_LINELEN, vobjFile) != NULL && feof(vobjFile) == 0) {
printf("this is the first loop\n");
while (strcmp(strLine, "BEGINTRANS\n") !=... (5 Replies)
Discussion started by: uday.sena.m
5 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I need to get an output that is the same as "ethtool -e eth0"
But I need to use another method that does not use the eth port ID (ethX).
Does anyone know of any method?
Thanks!! (3 Replies)
Discussion started by: h0ujun
3 Replies
10. Shell Programming and Scripting
Hi Experts,
Problem summary :
I am facing the below problem on huge files when the disk is getting full on the half way through the execution.
If the disk was already full , the commands fail & everything is fine.
Sample Code :
head_rec_data_file=`head -1 sample_file.txt`
cat... (9 Replies)
Discussion started by: Pruthviraj_shiv
9 Replies
LEARN ABOUT FREEBSD
gcore
GCORE(1) BSD General Commands Manual GCORE(1)
NAME
gcore -- get core images of running process
SYNOPSIS
gcore [-f] [-s] [-c core] [executable] pid
DESCRIPTION
The gcore utility creates a core image of the specified process, suitable for use with gdb(1). By default, the core is written to the file
``core.<pid>''. The process identifier, pid, must be given on the command line.
The following options are available:
-c Write the core file to the specified file instead of ``core.<pid>''.
-f Dumps all available segments, excluding only malformed and undumpable segments. Unlike the default invocation, this flag dumps map-
pings of devices which may invalidate the state of device transactions or trigger other unexpected behavior. As a result, this flag
should only be used when the behavior of the application and any devices it has mapped is fully understood and any side effects can
be controlled or tolerated.
-s Stop the process while gathering the core image, and resume it when done. This guarantees that the resulting core dump will be in a
consistent state. The process is resumed even if it was already stopped. The same effect can be achieved manually with kill(1).
FILES
core.<pid> the core image
HISTORY
A gcore utility appeared in 4.2BSD.
BUGS
Because of the ptrace(2) usage gcore may not work with processes which are actively being investigated with truss(1) or gdb(1). Addition-
ally, interruptable sleeps may exit with EINTR.
The gcore utility is not compatible with the original 4.2BSD version.
BSD
July 14, 2010 BSD