04-23-2020
Collect Core Dumps
Shows how to locate core files. It looks to me like you do not have any existing core dumps -- I was not sure of your platform, looks like Solaris.
The article has a branchpoint set of links to platform specific information.
Plus I do not think version 6 of java is supported any longer. So getting Oracle help may not exist.
If anyone else knows more, please correct me.
You do know that sending the SIGSEGV signal to a given process (as root) will force a dump. Not a good idea in a production environment.
10 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
I am unable to open the mimesender thread. I get the following message when clicking on https://www.unix.com/showthread.php?p=33233#post33233 : (2 Replies)
Discussion started by: dangral
2 Replies
2. SCO
After rebuilding the RAIDs on the SCO Unix, the following dialog appears when rebooting the machine.
Fssat: /dev/boot mounted
Mounted /stand filesystem
Fsstat: /dev/usr1 okay
Mounted /usr1 filesystem
(continues usr2, usr3,
Fsstat: /dev/usr4 okay
Panic: HTFS: Bad directory ino... (2 Replies)
Discussion started by: Mac Tire
2 Replies
3. Programming
Could any one please suggest me how to solve this......
when I compiled the program and tried to execute it as follows, it works fine under different inputs like:
./main -r 300 -w 3 -s 100
./main -r 600 -w 3 -s 1000
./main -r 10 -w 3 -s 100
But it fails when I tired to give the input as... (1 Reply)
Discussion started by: kumars
1 Replies
4. Forum Support Area for Unregistered Users & Account Problems
Hello,
I'd like to post a aix thread but I'm unable to.
Please let me know why this is happening.
Thanks.... (1 Reply)
Discussion started by: sullivjp
1 Replies
5. Shell Programming and Scripting
I have a weird situation in which the binary dumps core and gives bus error. But before dumping the core and throwing the buss error, it gives some output.
unfortunately I can't grep the output before core dump
db2bfd -b test.bnd
maxSect 15
Bus Error (core dumped)
But if I do ... (4 Replies)
Discussion started by: rakeshou
4 Replies
6. Shell Programming and Scripting
Segmentation fault(core dumped)
but I cant find core file any where. how to make it out?
I try the command:ulimit -c unlimited, I even added it to the .bashrc file.And I removed ulimit setting in /etc/init.d/function. And there's no ulimit setting in /etc/profile. And I tried sudo find /... (8 Replies)
Discussion started by: vistastar
8 Replies
7. Solaris
Hello,
I'm running a kill -QUIT on few process IDs (OS: Solaris) but the Thread Dump is empty.
Can you please help me get it back on?
Since I'm quite new to this, I'm not aware of the checks. Please let me know for the info required to debug this issue.
Thanks! (3 Replies)
Discussion started by: DevendraG
3 Replies
8. Shell Programming and Scripting
I used take thread dump when our application gets out of memory issue.
can any one help on check thread dump result.
where it will save tool to read thread dump.:wall:
date; kill -3 process_id; sleep 300; kill -3 process_id; sleep 300; kill -3 process_id;date (5 Replies)
Discussion started by: ram5019
5 Replies
9. Linux
How do i get pointer to thread's local storage or thread specific data while analyzing core dump for linux ?
i use pthread_setspecific to store some data in the pthread's local stoare.
my multi threaded program on linux crashed, and i want to see what is stored in current running thread's... (2 Replies)
Discussion started by: vishwasungal
2 Replies
10. Shell Programming and Scripting
Hello, I was wondering if someone can assist me. I have a file that I download from a mainframe to a RedHat Linux 5.5 server, the file is delimited by control underscore characters and the record is terminated by a control M (carriage return). The problem I am having is with the control M... (3 Replies)
Discussion started by: app1mvf
3 Replies
LEARN ABOUT ULTRIX
savecore
savecore(8) System Manager's Manual savecore(8)
Name
savecore - save a core dump of the operating system
Syntax
/etc/savecore [ options ] dirname [ system ] [ corename ]
Description
The command is meant to be called near the end of the file. The command saves the core dump of the system (assuming one was made) and
writes a reboot message in the shutdown log.
The command checks the core dump to be certain it corresponds with the current running ULTRIX. If it does, it saves the core image in the
file dirname/vmcore.n and saves the namelist in the file dirname/vmunix.n. The trailing .n in the pathnames is replaced by a number which
increments each time is run in that directory.
After saving the core and namelist images, will save the error logger buffer into a predetermined file. The error logger buffer contains
information about why the crash occurred. After completes, the daemon will extract the error logger file and translate its contents into a
form familiar to the program.
Before writes out a core image, it reads a number from the file dirname/minfree. If there are fewer free blocks on the filesystem that
contains dirname than the number obtained from the file, a core dump is not done. If the file does not exist, savecore always writes out
the core file (assuming that a core dump was taken).
The command also writes a reboot message in the shut down log. If the system crashed as a result of a panic, also records the panic string
in the shut down log.
For partial crash dumps, creates a sparse core image file in dirname/vmcore.n. If this sparse core image file is copied or moved to
another location, the file expands to its true size which can take too much file system space. Hence, to copy or move sparse core image
files, you must use the command. The command has a conversion option to create sparse output files.
Options
-c Clears the core dump. This option is useful when the core dump is corrupted in a way that will not allow to save it safely. Use the
option with caution, because once it clears the core dump, the core dump cannot be retrieved.
-d dumpdev dumplo
Specifies the dump device and the dump offset when running on a system image other than the currently running system image. The pro-
gram assumes that the running system image is and it reads the dump device and dump device offset are different in the system image
that crashed, the option provides the correct dump device and dump device offset.
-e Saves only the error logger buffer into a file. If used, core or namelist images are not saved.
-f corename
Takes the i corefile name as the file from which to extract the the crash dump data instead of the default dump device. This option
is used only for diskless workstations.
If the core dump was from a system other than /vmunix, the name of that system must be supplied as system. The program assumes that the
running image is
After successful completion, the core dump is cleared. Also, a message is written in the file which tells whether the dump succeeded or
failed.
Files
Shut down log
Current running ULTRIX system
See Also
dd(1), uerf(8)
savecore(8)