08-26-2011
Quote:
Originally Posted by
donadarsh
use string command to read all string from core and redirect it to some tmp file.
This is not the proper way to debug a core file. use a debugger like already suggested.
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
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
3. UNIX for Dummies Questions & Answers
Hi All,
is there any way to find out the optimal/would be size of the cor dump file generated by the system while a process got terminated abnormally?
Basically we have been asked to provide the size of the core dump file being generated by the administrators who maintained the UNIX boxes.... (4 Replies)
Discussion started by: pushp.gahlot
4 Replies
4. Programming
by what name does a core dump file stored???
like i wrote a test code:
//dump.c
main()
{
char *p=NULL;
printf("%s",p);
}
of course the above code will produce a segmentation fault. but i cant see any file named core in my CWD. am using SUN0S 5.9 (6 Replies)
Discussion started by: vikashtulsiyan
6 Replies
5. Programming
Hi All,
May be it is a stupid question, but, I would like to know what is the advantage using a core dump file at the moment of debugging using gdb.
I know a core dump has information about the state of the application when it crashed, but, what is the difference between debugging using the... (2 Replies)
Discussion started by: lagigliaivan
2 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. 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
8. Solaris
I am new to UNIX.
My Application is using c (.so files) and Java code.
My application crashes and CORE DUMP file is generated ,which is huge.
Now I want to view the CORE DUMP file to debug the application using dbx without starting process again.
By only using the CORE DUMP file and dbx ,can i... (1 Reply)
Discussion started by: satde
1 Replies
9. UNIX for Dummies Questions & Answers
Can any body provide me some good link to learn to create and analyze linux user mode application / kernel module core dumps? (1 Reply)
Discussion started by: rupeshkp728
1 Replies
10. Red Hat
Hello All,
I am new joiner of this forum.I am new to Linux shell scripting.
At present I have identified 1 application which stalls very frequently (PID is say xyz) and I am not having much information in its application log to identify the root cause of stalling. I need to take the core dump... (19 Replies)
Discussion started by: Anjan Ganguly
19 Replies
KDBG(1) General Commands Manual KDBG(1)
NAME
kdbg - a graphical debugger interface
SYNOPSIS
kdbg [ generic-options ] [ -t file ] [ -r device ] [ -l language ] [ -p pid ] [ program ] [ core ]
DESCRIPTION
KDbg is a graphical user interface to gdb, the GNU debugger. It provides an intuitive interface for setting breakpoints, inspecting vari-
ables, stepping through code and much more. KDbg requires KDE but you can of course debug any program.
KDbg can also debug XSLT (XML stylesheet translation) scripts by interfacing with xsldbg. Debian users must install the kxsldbg package to
make use of this feature.
You can pass KDbg the path of the executable to debug (program) or a core dump to debug (core).
Features of KDbg include:
Inspection of variable values in a tree structure.
Direct member: For certain compound data types the most important member values are displayed next to the variable name, so that it
is not necessary to expand the subtree of that variable in order to see the member value. KDbg can also display Qt's QString val-
ues, which are Unicode strings.
Debugger at your finger tips: The basic debugger functions (step, next, run, finish, until, set/clear/enable/disable breakpoint) are
bound to function keys F5 through F10. Quick and easy.
View source code, search text, set program arguments and environment variables, display arbitrary expressions.
Debugging of core dumps, attaching to running processes is possible.
Conditional breakpoints.
OPTIONS
Below are the kdbg-specific options. For a full summary of options, run kdbg --help.
-t file
Write a transcript of the conversation with the debugger to the given file.
-r device
Use remote debugging via the given device.
-l language
Specify the language of the program/script to debug. This must be either C (for a C/C++ program) or XSL (for an XSLT script). If
this option is not passed then KDbg will try to deduce the language from the given filename.
-p pid Attach to the process with the given process ID.
SEE ALSO
gdb(1), xsldbg(1).
Full user documentation is available through the KDE Help Centre. Alternatively the HTML documentation can be viewed directly from
/usr/share/doc/kdbg/html/.
AUTHOR
KDbg was written by Johannes Sixt <Johannes.Sixt@telecom.at>.
This manual page was prepared by Ben Burton <bab@debian.org> for the Debian GNU/Linux system (but may be used by others).
March 25, 2005 KDBG(1)