Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: unable to read core dumps on unix. Is there another way than using GDB?
Operating Systems Linux unable to read core dumps on unix. Is there another way than using GDB? Post 302596023 by suyogs on Tuesday 7th of February 2012 04:08:45 AM
Old 02-07-2012
unable to read core dumps on unix. Is there another way than using GDB?
hi all,
I am having set of core dumps obtained from client server. Now i am trying to read them but unable to do so.
I have few queries:
1. Core dumps were generated on some xyz server and copied to my unix virtual. Can I read them as text here?
2. I tried installing gdb-7.3 but when i fire "make" command it will show error message as:
Code:
configure: error: no termcap library found
make[1]: *** [configure-gdb] Error 1
make[1]: Leaving directory `/home/sshetye/gdb-7.3'
make: *** [all] Error 2

3. so i tried installing 'ncurses-5.5.tar' but again on 'make' command it is giving me error as:
Code:
cd ../objects;   -I../c++ -I../include -I. -DHAVE_CONFIG_H -I. -I../include  -D_GNU_SOURCE -DNDEBUG  -c ../c++/cursesf.cc
/bin/sh: -I../c++: No such file or directory
make[1]: *** [../objects/cursesf.o] Error 127
make[1]: Leaving directory `/home/sshetye/ncurses-5.5/c++'
make: *** [all] Error 2

How can I resolve these errors?
4. Is there any another way to read core dumps in text format, instead using GDB?
Note: output of command "file core.11249_gcws2145" is as below:
ELF 64-bit LSB core file AMD x86-64, version 1 (SYSV), SVR4-style, from 'submit_xup.pl'

5. I fed up with installing GDB on my machine, please let me know if there is any another way to read core dumps in text format.

[For moderators: there are threads which are some how similar to my problem, but not exactly matching my requirements and these threads are old enough too, so i have created this new thread].


Thanks in advance,
Suyog

---------- Post updated 02-07-12 at 04:08 AM ---------- Previous update was 02-06-12 at 09:54 AM ----------

Hi all,
I able to install gdb-7.3 at my unix virtual. But still i am unable to read core dumps. tried with this command " gdb -c core.11249_gcws2145" but output as:
Code:
[New LWP 11288]
[New LWP 11286]
[New LWP 11249]
Core was generated by `/usr/bin/perl /home/ssl/bin/submit_xup.pl LARGE'.
Program terminated with signal 11, Segmentation fault.
#0  0x0000003a4de08219 in ?? ()
(gdb)

I won't be able to read whole core dump file.
What will be the command to read core dump which is in binary form??
Please reply.

Thanks,
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

reading core dumps

Does anyone know how to read core dumps. Is gdb the only tool for it ? The OS is Solaris. Thanks (2 Replies)
Discussion started by: suntan
2 Replies

2. Solaris

Generating core dumps

I have the following set up on a Sun server running solaris 5.8 for core dump generation coreadm global core file pattern: /var/core init core file pattern: /var/core global core dumps: enabled per-process core dumps: enabled global setid core dumps:... (4 Replies)
Discussion started by: handak9
4 Replies

3. Programming

strcmp core dumps

hi everyone, Right now when I do: strcmp(s1, s2); i get a core dump because at times s1 or s2 can be nothing so that makes strcmp() core dump. What is the solution, if at times I expect one of them (or both) to be NULL? I want to be able to compare that s1 is NULL and s2 is "blah" or... (6 Replies)
Discussion started by: annie
6 Replies

4. SCO

SCO 5.07 Panic / Core Dumps

Anyone know how you go about interrogating a panic / core dump with crash for SCO Unix (5 Replies)
Discussion started by: ccarcher
5 Replies

5. UNIX for Advanced & Expert Users

Using GDB to analyse different CORE dumps

Hi, Can we modify the GDB source code so as to analyze core dumps from different targets? From my analysis, I think we need to build our section table statically for each target. i.e., including the various address boundaries in build_section_table() function. If this is the case, then the GDB... (2 Replies)
Discussion started by: nsdeeps
2 Replies

6. Programming

AIX core dumps

My program is not dumping core when hitting a segmentation violation inside a thread. However, it dumps core when the segv occurs within main. Any ideas on how to diagnose this? AIX 5.3 (4 Replies)
Discussion started by: bean66
4 Replies

7. Solaris

core dumps

i had a situation where a process was defunct. preap would not reap the process and gcore would not work properly (not sure why). therefore, the suggestion was to force a panic and collect the core dump. obviously you could do a savecore -L and capture the dump without bringing down the system.... (3 Replies)
Discussion started by: pupp
3 Replies

8. Red Hat

generating core dumps

Hi I have a Fedora installed and I try to generate my application's core dump file. My system has no coredump limit: $ ulimit core file size (blocks, -c) unlimited But when my application crashes no core dumps generated. I can generate dump file using gcore but it is not appropraite... (1 Reply)
Discussion started by: xyzt
1 Replies

9. Programming

Stack only core dumps

I'm working on a program in Linux with a group of people scattered around the country. When we have a crash, I like to send a core dump to the appropriate person so that they can understand the problem better. The problem is that our application uses several gigabytes worth of data and these... (4 Replies)
Discussion started by: bmsterner
4 Replies

10. HP-UX

Generate core dumps

kill -SEGV <pid> gives me the core file for that process but also terminates the process. Can I not get the core dump without terminating the process ? (2 Replies)
Discussion started by: mohtashims
2 Replies

LEARN ABOUT FREEBSD

crashinfo

CRASHINFO(8)						    BSD System Manager's Manual 					      CRASHINFO(8)

NAME

     crashinfo -- analyze a core dump of the operating system

SYNOPSIS

     crashinfo [-d crashdir] [-n dumpnr] [-k kernel] [core]

DESCRIPTION

     The crashinfo utility analyzes a core dump saved by savecore(8).  It generates a text file containing the analysis in the same directory as
     the core dump.  For a given core dump file named vmcore.XX the generated text file will be named core.txt.XX.

     By default, crashinfo analyzes the most recent core dump in the core dump directory.  A specific core dump may be specified via either the
     core or dumpnr arguments.	Once crashinfo has located a core dump, it analyzes the core dump to determine the exact version of the kernel
     that generated the core.  It then looks for a matching kernel file under each of the subdirectories in /boot.  The location of the kernel
     file can also be explicitly provided via the kernel argument.

     Once crashinfo has located a core dump and kernel, it uses several utilities to analyze the core including dmesg(8), fstat(1), iostat(8),
     ipcs(1), kgdb(1), netstat(1), nfsstat(1), ps(1), pstat(8), and vmstat(8).

     The options are as follows:

     -d crashdir
	     Specify an alternate core dump directory.	The default crash dump directory is /var/crash.

     -n dumpnr
	     Use the core dump saved in vmcore.dumpnr instead of the latest core in the core dump directory.

     -k kernel
	     Specify an explicit kernel file.

SEE ALSO

     textdump(4), savecore(8)

HISTORY

     The crashinfo utility appeared in FreeBSD 6.4.

BSD
								   June 28, 2008							       BSD
All times are GMT -4. The time now is 09:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy