Sponsored Content
Full Discussion: How to do core dump analysis
Top Forums UNIX for Advanced & Expert Users How to do core dump analysis Post 73679 by vijaysabari on Friday 3rd of June 2005 08:50:23 AM
Old 06-03-2005
Dbx debugger to analysis coredumps ......

dbx debugger is used to analysis the coredumps ............. i will explain with anexample

cc -g first.c
dbx ./a.out


Reading a.out
Reading ld.so.1
Reading libc.so.1
Reading libdl.so.1
Reading libc_psr.so.1
(dbx 1) sif main
(2) stop infunction main
(dbx 2) run
Running: a.out
(process id 6156)
stopped in main at line 7 in file "first.c"
7 printf("%d\n",time(&t1));
(dbx 3) n
1117798709
stopped in main at line 8 in file "first.c"
8 for ( i=0 ; i<10; i++ ){
(dbx 4) n
stopped in main at line 9 in file "first.c"
9 printf("%d\n",rand());
(dbx 5) n
16838
stopped in main at line 8 in file "first.c"
8 for ( i=0 ; i<10; i++ ){
(dbx 6) exitbx 6)
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

help, what is the difference between core dump and panic dump?

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

core file analysis

Hi folks, I'm hoping someone would be charitable enough to give me a quick explanation of adb usage for analyzing core files...or point me in the right direction. A search here revealed scant results and web searches are providing me with ambiguous information. Running Solaris. Thanks,... (1 Reply)
Discussion started by: kristy
1 Replies

3. UNIX for Advanced & Expert Users

any tool for core analysis on HP-UX?

Hi, I just wanted to know is there any tool avaliable for core analysis on hp-ux. I have heard about q4 utility. But I think it is used for analysis of system crash dump and not for core dump produced by a user process. gdb doesn't give much information unless the binary is debug-build. ... (0 Replies)
Discussion started by: shriashishpatil
0 Replies

4. UNIX for Advanced & Expert Users

Core Dump Analysis Using PStack and PMAP

Hello, I'm new to the group and this is my first post. I'm hoping someone can help me out. I have a core dump that I need to analyze from a Unix box and I've never done this sort of thing before. I was told to run a pmap and pstack on the core file which provided two different output files. ... (3 Replies)
Discussion started by: kimblebee
3 Replies

5. AIX

How to do core dump analysis in AIX?

Please tell me some methods to analyse core dump in AIX.:) (2 Replies)
Discussion started by: Mythili
2 Replies

6. Solaris

Core file analysis

How can we analyze a core file and determine why it was generated on a solaris system? I know file core filename will tell us what program generated the file. But, what to do next to get more details? Thanks, (5 Replies)
Discussion started by: Pouchie1
5 Replies

7. Red Hat

core dump analysis : __kernel_vsyscall ()

We have just enabled core dump on our RHEL5.7 OS. the java process is terminating very often so we enable core dump to analysis the issue and find below in core dump file. Core was generated by `/usr/java/jdk1.6.0_06//bin/java -server -Xms1536m -Xmx1536m -Xmn576m -XX:+Aggre'. Program... (0 Replies)
Discussion started by: pawankkamboj
0 Replies

8. UNIX for Dummies Questions & Answers

Learn Linux Core Dump Analysis

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

9. AIX

AIX system dump analysis

dear all, i have p770 aix6.1 last week, the host reboot suddenly with dump. but i don't know how to analyze the dump. I posted kdb details in the attachment. please anybody help me. #>kdb vmcore.0 /unix vmcore.0 mapped from @ 700000000000000 to @ 7000001c72c0908 START ... (13 Replies)
Discussion started by: tomato00
13 Replies
ddd(1)								     GNU Tools								    ddd(1)

NAME
ddd, xddd - The Data Display Debugger SYNOPSIS
ddd [--help] [--gdb] [--dbx] [--ladebug] [--wdb] [--xdb] [--jdb] [--pydb] [--perl] [--debugger name] [--[r]host [username@]hostname]] [--trace] [--version] [--configuration] [options...] [prog[core|procID]] but usually just ddd program DESCRIPTION
DDD is a graphical front-end for GDB and other command-line debuggers. Using DDD, you can see what is going on "inside" another program while it executes--or what another program was doing at the moment it crashed. DDD can do four main kinds of things (plus other things in support of these) to help you catch bugs in the act: o Start your program, specifying anything that might affect its behavior. o Make your program stop on specified conditions. o Examine what has happened, when your program has stopped. o Change things in your program, so you can experiment with correcting the effects of one bug and go on to learn about another. "Classical" UNIX debuggers such as the GNU debugger (GDB) provide a command-line interface and a multitude of commands for these and other debugging purposes. DDD is a comfortable graphical user interface around an inferior GDB, DBX, Ladebug, XDB, JDB, Python debugger, or Perl debugger. DDD is invoked with the shell command ddd. You can open a program to be debugged using `File->Open Program' (the `Open Program' item in the `File' menu. You can get online help at any time using the `Help' menu; for the first steps, try `Help->What Now?'. Quit DDD using `File->Exit'. More information on DDD is contained in the DDD Manual. You can read the text-only version in DDD (via `Help->DDD Reference') or in Emacs (as Info file). Full-fledged HTML, PostScript, and PDF versions are available online via the DDD WWW page, http://www.gnu.org/software/ddd/ OPTIONS
These are the most important options used when starting DDD. All options may be abbreviated, as long as they are unambiguous; single dashes may also be used. DDD also understands the usual X options such as `-display' or `-geometry'; see X(1) for details. All arguments and options not handled by DDD are passed to the inferior debugger. To pass an option to the inferior debugger that con- flicts with an X option, or with a DDD option listed here, use the `--debugger' option, below. --configuration Show the DDD configuration settings and exit. --dbx Run the DBX debugger as inferior debugger. --debugger name Invoke the inferior debugger name. This is useful if you have several debugger versions around, or if the inferior debugger cannot be invoked as `gdb', `dbx', `xdb', `jdb', `pydb', or `perl' respectively. This option can also be used to pass options to the inferior debugger that would otherwise conflict with DDD options. For instance, to pass the option `-d directory' to XDB, use: ddd --debugger "xdb -d directory" If you use the `--debugger' option, be sure that the type of inferior debugger is specified as well. That is, use one of the options `--gdb', `--dbx', `--xdb', `--jdb' `--pydb', or `--perl' (unless the default setting works fine). --gdb Run the GDB debugger as inferior debugger. --help Give a list of frequently used options. Show options of the inferior debugger as well. --host [username@]hostname Invoke the inferior debugger directly on the remote host hostname. If username is given and the `--login' option is not used, use username as remote user name. --jdb Run JDB as inferior debugger. --ladebug Run Ladebug as inferior debugger. --perl Run Perl as inferior debugger. --pydb Run PYDB as inferior debugger. --rhost [username@]hostname Run the inferior debugger interactively on the remote host hostname. If username is given and the `--login' option is not used, use username as remote user name. --trace Show the interaction between DDD and the inferior debugger on standard error. This is useful for debugging DDD. If `--trace' is not specified, this information is written into `$HOME/.ddd/log', such that you can also do a post-mortem debugging. --version Show the DDD version and exit. --wdb Run the WDB debugger as inferior debugger. --xdb Run XDB as inferior debugger. A full list of options, including important options of the inferior debugger, can be found in the DDD manual. SEE ALSO
X(1), gdb(1), dbx(1), wdb(1), xdb(1), perldebug(1) `ddd' entry in info. `gdb' entry in info. Debugging with DDD: User's Guide and Reference Manual, by Andreas Zeller. Using GDB: A Guide to the GNU Source-Level Debugger, by Richard M. Stallman and Roland H. Pesch. Java Language Debugging, at http://java.sun.com/ (and its mirrors) in /products/jdk/1.1/debugging/ The Python Language, at http://www.python.org/ and its mirrors. DDD--A Free Graphical Front-End for UNIX Debuggers, by Andreas Zeller and Dorothea Luetkehaus, Computer Science Report 95-07, Technische Universitaet Braunschweig, 1995. DDD - ein Debugger mit graphischer Datendarstellung, by Dorothea Luetkehaus, Diploma Thesis, Technische Universitaet Braunschweig, 1994. The DDD FTP site, ftp://ftp.gnu.org/ The DDD WWW page, http://www.gnu.org/software/ddd/ The DDD Mailing List, ddd@gnu.org For more information on this list, send a mail to ddd-request@gnu.org . COPYRIGHT
This manual page is Copyright (C) 2001 Universitaet Passau, Germany. Permission is granted to make and distribute verbatim copies of this manual page provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual page under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual page into another language, under the above conditions for modi- fied versions, except that this permission notice may be included in translations approved by the Free Software Foundation instead of in the original English. DDD 3.3.1 2001-01-15 ddd(1)
All times are GMT -4. The time now is 08:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy