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
gcore(1) User Commands gcore(1)
NAME
gcore - get core images of running processes
SYNOPSIS
gcore [-pgF] [-o filename] [-c content] process-id...
DESCRIPTION
The gcore utility creates a core image of each specified process. By default, the name of the core image file for the process whose process
ID is process-id will be core.process-id.
OPTIONS
The following options are supported:
-c content Produces core image files with the specified content. The content description uses the same tokens as in coreadm(1M). The
-c option does not apply to cores produced due to the -p or -g flags.
-F Force. Grabs the target process even if another process has control.
-g Produces core image files in the global core file repository with the global content as configured by coreadm(1M). The com-
mand will fail if the user does not have permissions to the global core file repository.
-o filename Substitutes filename in place of core as the first part of the name of the core image files. filename can contain the same
tokens to be expanded as the paths in coreadm(1M).
-p Produces a core image file in the process-specific location with the process-specific content for each process as config-
ured by coreadm(1M). The command will fail if the user does not have permissions to the per-process core file repository.
OPERANDS
The following operand is supported:
process-id process ID
EXIT STATUS
The following exit values are returned:
0 On success.
non-zero On failure, such as non-existent process ID.
FILES
core.process-id core images
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWtoo |
+-----------------------------+-----------------------------+
|Interface Stability |See below. |
+-----------------------------+-----------------------------+
Command Syntax is Evolving. Output Format(s) are Unstable.
SEE ALSO
kill(1), coreadm(1M), setrlimit(2), core(4), proc(4), attributes(5)
NOTES
gcore is unaffected by the setrlimit(2) system call using the RLIMIT_CORE value.
SunOS 5.10 11 Feb 2004 gcore(1)