05-11-2004
Once Again, Thanks Driver.
I have HP-UX.
I was tracing out the function that has caused the memory core dump.
The Complier is set internally with some option. It is not set with debugging option. Also I cannot set the debugging options externally.
Does there any other command like 'bt' in gdb to trace to the line that has caused the core dump?
Any other possibility on setting break points?
Thanks and Regards,
P. Prathaban.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
2. UNIX for Dummies Questions & Answers
does any one have read a core dump?
is there any reader for that? or may i know what is the use of that core which takes sometimes memory in GBs?
:) (6 Replies)
Discussion started by: sskb
6 Replies
3. UNIX for Dummies Questions & Answers
Hi ,
Working on AIX 4.3. An internal error from my apps engine suddenly causes the engine to die. During this time i do notice a core file being dumped in the directory from where I try to re-start my engine.
Q is how does one read this core file, or I should say 'what is this core file'?
thnx (2 Replies)
Discussion started by: buRst
2 Replies
4. UNIX for Dummies Questions & Answers
I've got a core dump in my weblogic home directory, which i have tried to debug by initiating savecore from /etc/init.d/savecore start
but savecore failed to create the two files, that is vmcore.n and vmunix.n.
savecore is enable on my server to save vmcore and vmunix in /var/crash/hostname
1)... (4 Replies)
Discussion started by: hassan2
4 Replies
5. Programming
MY friends:
my program under sco unix have a problem?
it create a core dump file on the path when execute program ,
but i can't find the error of the C program ,i don't know how to
see the error about my program use core, please help me
or give me some suggest and what tools can use... (1 Reply)
Discussion started by: zhaohaizhou
1 Replies
6. UNIX for Advanced & Expert Users
Hi All,
i am new to this forum.i want detail of reading the core file and trace the problem because of what the program get crashed.please help me.if any body knows any website or tutoril plese let me know.
sudhir (6 Replies)
Discussion started by: sudhir patnaik
6 Replies
7. UNIX for Dummies Questions & Answers
Hi All
I am new for this forum. I have a core file by using gdb and bt cmd I got the function name but I want to the exact cause of the core dump because of I can not reproduse the binary so if any one know the cmd plz plz plz let me know. (0 Replies)
Discussion started by: gyanusoni
0 Replies
8. UNIX for Dummies Questions & Answers
my progrme complaints 'Segmentation fault'.
How to let it print 'Segmentation fault(core dumped)' and generate core dump file?
$ulimit
unlimited (22 Replies)
Discussion started by: vistastar
22 Replies
9. HP-UX
Hi Guys,
I was wondering if somebody could give me a link to a very good source of information or document about core dump process and How to's about it. I have also googled it and found some articles myself.
Thanks
Messi (1 Reply)
Discussion started by: messi777
1 Replies
10. Solaris
Hi guys,
just want to know which core file pattern is best to set for core dumps:
1) per-process file name pattern
or
2) global file name pattern.
I will really appreciate an explanation why the chosen one is better.
Thanks a lot guys. (2 Replies)
Discussion started by: cjashu
2 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