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
DUMP(1M) DUMP(1M)
NAME
dump - incremental file system dump
SYNOPSIS
dump [ key [ argument ... ] filesystem ]
DESCRIPTION
Dump copies to magnetic tape all files changed after a certain date in the filesystem. The key specifies the date and other options about
the dump. Key consists of characters from the set 0123456789fusd.
f Place the dump on the next argument file instead of the tape.
u If the dump completes successfully, write the date of the beginning of the dump on file `/etc/ddate'. This file records a separate
date for each filesystem and each dump level.
0-9 This number is the `dump level'. All files modified since the last date stored in the file `/etc/ddate' for the same filesystem at
lesser levels will be dumped. If no date is determined by the level, the beginning of time is assumed; thus the option 0 causes the
entire filesystem to be dumped.
s The size of the dump tape is specified in feet. The number of feet is taken from the next argument. When the specified size is
reached, the dump will wait for reels to be changed. The default size is 2300 feet.
d The density of the tape, expressed in BPI, is taken from the next argument. This is used in calculating the amount of tape used per
write. The default is 1600.
If no arguments are given, the key is assumed to be 9u and a default file system is dumped to the default tape.
Now a short suggestion on how perform dumps. Start with a full level 0 dump
dump 0u
Next, periodic level 9 dumps should be made on an exponential progression of tapes. (Sometimes called Tower of Hanoi - 1 2 1 3 1 2 1 4 ...
tape 1 used every other time, tape 2 used every fourth, tape 3 used every eighth, etc.)
dump 9u
When the level 9 incremental approaches a full tape (about 78000 blocks at 1600 BPI blocked 20), a level 1 dump should be made.
dump 1u
After this, the exponential series should progress as uninterrupted. These level 9 dumps are based on the level 1 dump which is based on
the level 0 full dump. This progression of levels of dump can be carried as far as desired.
FILES
default filesystem and tape vary with installation.
/etc/ddate: record dump dates of filesystem/level.
SEE ALSO
restor(1), dump(5), dumpdir(1)
DIAGNOSTICS
If the dump requires more than one tape, it will ask you to change tapes. Reply with a new-line when this has been done.
BUGS
Sizes are based on 1600 BPI blocked tape. The raw magtape device has to be used to approach these densities. Read errors on the filesys-
tem are ignored. Write errors on the magtape are usually fatal.
DUMP(1M)