10-19-2007
Quote:
And. No way should an app 'be expected' to dump core in production.
Why is that so Jim ?
Did you mean an app running in production to be cent percent perfect all the time ? I accept that bugs that dump core in production are not a welcoming feature.
But I believe neither of the code that is written could be ever said 100% bug free, so core dumps in production are more like a way of life and they are bound to happen.
I didn't mean to say anything negatively and only point I would like to stress is " it happens " ( I know its a lame excuse and hate that myself very much )
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. UNIX for Advanced & Expert Users
Every time I reboot our solaris 9 (SunOS 5.9 Generic_118558-19 sun4u sparc SUNW,Sun-Fire-480R) box,
I get the messages below:
# dmesg | grep dump
Mar 24 12:39:55 hostname savecore: initial dump header corrupt
Mar 24 12:39:55 hostname genunix: dump on /dev/dsk/c1t0d0s1 size 700 MB
Mar 24... (2 Replies)
Discussion started by: xnightcrawl
2 Replies
6. Red Hat
Hi All,
I just wondering how can we read core files (core.****). I have an appication, when it is trying to crash I got the coredump. since it is in binary format, I dont know how to read that. Thanks (1 Reply)
Discussion started by: s_linux
1 Replies
7. HP-UX
Hi all,
I am quite weak in C but I need to get some work done. Hope someone can help me out. I keep getting this error when i try to run my C application in my HP-UX 10.20 machine.
Some code snippet:
Month(DBTime) =====This is a function which will return variable "CutOffTime" to be use... (5 Replies)
Discussion started by: Vision©
5 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
KGDB(1) BSD General Commands Manual KGDB(1)
NAME
kgdb -- kernel debugger
SYNOPSIS
kgdb [-a | -f | -fullname] [-b rate] [-q | -quiet] [-v] [-w] [-d crashdir] [-c core | -n dumpnr | -r device] [kernel [core]]
DESCRIPTION
The kgdb utility is a debugger based on gdb(1) that allows debugging of kernel core files.
The options are as follows:
-a Increase the annotation level. An annotation level of 1 features the historical -fullname option of gdb(1). This is useful
when running kgdb in Emacs. The -f or -fullname options are supported for backward compatibility as well.
-b rate Set the baudrate to rate.
-q Suppress printing of the banner when the debugger starts. The -quiet form is supported for compatibility as well.
-v Increase verbosity.
-w Opens kmem-based targets in read-write mode. (This is identical to what --wcore used to do in previous gdb versions for
FreeBSD.)
-d crashdir Use crashdir instead of the default, /var/crash to locate kernel core dump files in. The name vmcore. plus the dump number will
be appended to determine the actual dump file name.
-c core Explicitly use core as the core dump file.
-n dumpnr Use the kernel core dump file numbered dumpnr for debugging.
-r device Use device to connect kgdb to for a remote debugging session.
The -c, -n, and -r options are mutually exclusive.
Optionally, the name of the kernel symbol file and the name of the core dump file can be supplied on the command-line as positional argu-
ments. If no kernel symbol file name has been given, the symbol file of the currently running kernel will be used. If no core dump file has
been specified through either of the options or the last command-line argument, /dev/mem will be opened to allow debugging the currently run-
ning kernel.
FILES
/dev/mem Default memory image to open if no core dump file has been specified.
/var/crash Default directory to locate kernel core dump files.
SEE ALSO
gdb(1)
HISTORY
The kgdb utility first appeared in its current form in FreeBSD 5.3.
BSD
October 11, 2006 BSD