03-24-2006
core dumps for anything are not normal behavior. The only ways this could happen:
One process is signaling another with SIGABRT or some other sinal that forces a core dump. This is odd behavior and I've not seen it.
Some process itself had a bus error or a segfault, which means there is a problem with the process code. Or a shared library. This sometimes happens when there are upgrades or patches applied to a sytem.
It may also be that the process cannot do what it is supposed to do - maybe it has been started at the wrong time. Or run on a system that is not configured to do what the process expects. Or a control file for the process is corrupted....
Yes, you need to research it and fix it if possible.
10 More Discussions You Might Find Interesting
1. Programming
i create one executed file (based on c language). when 1 try to
executed the file, the result show me the bus error (coredump).
can you help me to solve this problem. thanks. (2 Replies)
Discussion started by: lala
2 Replies
2. Solaris
I am trying to set up coredumps on a server, I have enabled the coreadm, and have also set a path to whre the coredumps will go.
I now need to set the ulimit , as this is set to 0. I made the change:
ulimit -c 8192
but when I logged out and back in, it was set back to 0 again. I need to know... (1 Reply)
Discussion started by: mzyvn6
1 Replies
3. Programming
haiu all
what makes strncpy to coredump (0 Replies)
Discussion started by: vijaysabari
0 Replies
4. Solaris
SunOS unknown 5.9 Generic_118558-10 sun4u sparc SUNW,Sun-Fire-880
I'm trying to set up mirroring and am running into a problem:
As you can see, I set up the metadb, but am getting a coredump when running metainit. I saw this through google, but don't know the validity of it. Any ideas?
#... (5 Replies)
Discussion started by: dangral
5 Replies
5. Solaris
Hi Guru's
Can any want here could explain to me the different between soft reboot and hard reboot .
Best Regards
Seelan (3 Replies)
Discussion started by: seelan3
3 Replies
6. UNIX for Dummies Questions & Answers
This works for all my normal executions. But on one machine, a coredump is expected on one command. We don't care and know it will always happen, but need to confirm the version info from the start of the output. This is output from the exe:
$ ./Up
-*-*- XXXXXXX UPDATE XXXXX Version... (7 Replies)
Discussion started by: brdholman
7 Replies
7. Solaris
Getting memory fault (coredump) and segmentation fault(coredump)
when i tried javac or java -version. what could be the problem?
Regards
Eswar (2 Replies)
Discussion started by: BhuvanEswar
2 Replies
8. AIX
Hello!
I do have an IBM pSeries 7043 server running AIX 5.2.0.0. Well, I do have trouble to run xsnaadmin tool remotely, I mean, the xsnaadmin tool can't run on exported X display.
What I'm doing is
aixserver>export DISPLAY=xxx.xxx.xxx.xxx:0.0
aixserver>xsnaadmin
Segmentation... (0 Replies)
Discussion started by: jssanche
0 Replies
9. Shell Programming and Scripting
Hi Gurus,
I tried bc 1000 % 10 on tcsh and ksh and its throwing a core dump on a sun solaris machine.
uname -a
SunOS azote 5.9 Generic_118558-39 sun4u sparc SUNW,Ultra-4
Please let me know if you find anything.
Thanks,
Kinny (8 Replies)
Discussion started by: kinny
8 Replies
10. HP-UX
Hi,
I'm looking for the help on how to implement coredump using the tools that comes with HP-UX 11.23 and HP-UX 11.31.
To also avoid the the dump files fill-up the root disk when dump occurs.
I'm new to this and would need step by step please.
Thanks in advance! (3 Replies)
Discussion started by: lamoul
3 Replies
reboot(8) System Manager's Manual reboot(8)
NAME
reboot - Restarts the machine
SYNOPSIS
/usr/sbin/reboot [-dlnq]
DESCRIPTION
When the system is running and multiple users are logged in, use the shutdown -r command to perform a reboot operation. If no users are
logged in, use the reboot command.
The reboot command normally stops all running processes, syncs the disks, logs the reboot, and writes a shutdown entry in the login
accounting file, /var/adm/wtmp.
The reboot command uses the sync call to synchronize the disks, and to perform other shutdown activities such as resynchronizing the hard-
ware time-of-day clock. After these activities, the system reboots. By default, the system starts and the file systems are automatically
checked. If the start-up activities are successful, the system comes up in the default run-level.
You must have root privileges to use this command. Using the -n flag can result in file system damage.
FLAGS
Generates a crash dump of the system before halting it. Can be used with any of the other flags. Does not log the reboot using syslog
Does not sync the disks or log the reboot using syslog Performs a quick reboot without first shutting down running processes; does not log
the reboot using syslog
EXAMPLES
To enable the default reboot action, enter: reboot This command causes the system to stop all running processes, sync the disks, log the
shutdown, and perform other routine shutdown and reboot activities. To shut down the system without logging the reboot, enter: reboot -l
This command shuts down the system and performs all shutdown and reboot activities, except logging the shutdown. To reboot the system
abruptly, enter: reboot -q This command reboots the system abruptly without shutting down running processes.
FILES
Specifies the command path Specifies the login accounting file Specifies the path of the syslog daemon
RELATED INFORMATION
Commands: fsck(8), halt(8), init(8), savecore(8) shutdown(8), syslogd(8)
Functions: reboot(2), sync(2), syslog(3) delim off
reboot(8)