Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Stack only core dumps
Top Forums Programming Stack only core dumps Post 302470902 by bmsterner on Thursday 11th of November 2010 10:51:32 AM
Old 11-11-2010
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 core dumps are very large. Sending these core dumps is getting difficult.

From my experience, all I really need from a core dump is the stack. I'll look at the back trace in gdb, and maybe inspect some local variables. Is there a way to tell Linux only to dump the stack rather than all memory?

I've tried using "ulimit -c" to change the upper limit on the size of the core dump but there doesn't seem to be any guarantee that this will include the stack. In my case, these truncated core dumps don't produce a backtrace in gdb.

Another thought that I had is that there may be a utility out there that will extract the stack from the core dump and produce a second, smaller core dump. I've been searching for a while and I can't find anything. Does anyone have any suggestions?

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. Ubuntu

enabling core dumps for daemon processes

Hello, I am debugging a program which works as daemon. It sigfaults, unfortunately I'm unable to generate core dump file. Here is what I am doing: tsurko@bastila:~$ ulimit -c unlimited tsurko@bastila:~$ ulimit -c unlimited tsurko@bastila:~$ cat /etc/sysctl.conf | grep 'core_pattern'... (1 Reply)
Discussion started by: tsurko
1 Replies

9. 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

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

kgdb

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
All times are GMT -4. The time now is 01:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy