Retrieving symbol information from crash dump on Mac OS X


 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications Retrieving symbol information from crash dump on Mac OS X
# 1  
Old 02-04-2010
Retrieving symbol information from crash dump on Mac OS X

I am initiating the discussion.Hope everyone will add on to this.
Whenever any application crashes the system's crash reporter(/System/Library/CoreServices/Crash Reporter.app) creates a crash dump.A crash dump is the image of the state of the kernel that was in physical memory when the system failed.The crash log contains a stack trace with whatever program symbol information found in the application.And if the application has stripped of its debugginginformation(release build),no usefull information about the application's stack will be logged.In such situations we can use the atos("address to symbol") tool to convert these addresses back to their symbolic names. It may help us to diagnose and fix the underlying problem causing the crash. Because the TempConverter executable has no symbol information, program locations in the TempConverter code segment are listed as hexadecimal offsets. If enough debugging information is available, the tool also supplies the source file name and line number for the address.

Thanks
Eliza

Last edited by pludi; 02-04-2010 at 04:08 AM.. Reason: removed link
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. HP-UX

Prevent crash dump when SG cluster node reboots

Hi Experts, I have configured HP-UX Service Guard cluster and it dumps crash every time i reboot a cluster node. Can anyone please help me to prevent these unnecessary crash dumps at the time of rebooting SG cluster node? Thanks in advance. Vaishey (2 Replies)
Discussion started by: Vaishey
2 Replies

2. Solaris

dedicated crash dump device

Hello Guys, I need a little help here. I have been studying crash dump and per what I am reading, you can dedicate a slice to use as a dump device. Now when you dedicate this slice, do you have to : 1) create a mount point? 2) add entry in /etc/vfstab? 3) is this slice wu or wm? 4) should... (3 Replies)
Discussion started by: cjashu
3 Replies

3. Solaris

copy crash dump file

Hi gurus, I will be glad if anyone can help me with this: How do you copy a crash dump file to send to your support provider? Thanks lots guys. (1 Reply)
Discussion started by: cjashu
1 Replies

4. Solaris

Solaris 10 zone crash dump file?

Hi, I'm running Solaris 10 with a zone called "testzone" If I do a "reboot -d" on the host, as expected the kernet panics, reboots and creates a crash dump file in /var/crash However no crash file is created in testzone. My question is how can I tell if a zone crashs or shuts down... (4 Replies)
Discussion started by: fastexit
4 Replies

5. UNIX for Dummies Questions & Answers

analyze linux crash dump

Can anybody let me know the steps how can I produce a crash dump and then analyze it? (4 Replies)
Discussion started by: rupeshkp728
4 Replies

6. Solaris

Sparc Solaris 8 crash dump

My sparc solaris 8 server crashed/rebooted yesterday and I have the vmcore files. I have some initial output from SCAT and ACT. I have not included all but any info would be helpful. I can supply more output if necessary. Thanks you. Can I have any information about this ACT and SCAT... (2 Replies)
Discussion started by: csgonan
2 Replies

7. Solaris

crash dump

hi , i have machine that is crashed how i can enable core dump file & how can i find it ? :confused: (4 Replies)
Discussion started by: lid-j-one
4 Replies

8. Linux

crash dump server for red hat ent 4

Is it true that you can't have the crash dump server/client on the same server? I know I've installed Nagios open source before, I though it's only for that kind of thing. I never though that Red hat ent 4 would be like client/server on the crash dump. if someone is having problem with high... (0 Replies)
Discussion started by: itik
0 Replies

9. Solaris

crash dump

Can anyone of you help me in enabling crash dump on Solaris 5.5.1 (1 Reply)
Discussion started by: csreenivas
1 Replies

10. HP-UX

crash dump

hi friends, i know that when there is a crash then that memory image is put into /var/adm/crash but if the system hangs up and if i have access to console of that machine then how can i take the crash dump manully. thanks (2 Replies)
Discussion started by: mxms755
2 Replies
Login or Register to Ask a Question
expand_dump(8)						      System Manager's Manual						    expand_dump(8)

NAME
expand_dump - Produces a non-compressed kernel crash dump file SYNOPSIS
/usr/sbin/expand_dump input-file output-file DESCRIPTION
By default, kernel crash dump files (vmzcore.#) are compressed during the crash dump. Compressed core files can be examined by the latest versions of debugging tools that have been recompiled to support compressed crash dump files. However, not all debugging tools may be upgraded on a given system, or you may want to examine a crash dump from a remote system using an older version of a tool. The expand_dump utility produces a file that can be read by tools that have not been upgraded to support compressed crash dump files. This non-compressed version can also be read by any upgraded tool. This utility can only be used with compressed crash dump files, and does not support any other form of compressed file. You cannot use other decompression tools such as compress, gzip, or zip on a compressed crash dump file. Note that the non-compressed file will require significantly more disk storage space as it is possible to achieve compression ratios of up to 60:1. Check the available disk space before running expand_dump and estimate the size of the non-compressed file as follows: Run tests by halting your system and forcing a crash as described in the Kernel Debugging manual. Use an upgraded debugger to determine the value of the variable dumpsize. Multiply this vale by the 8Kb page size to approximate the required disk space of the non-compressed crash-dump. Run expand_dump and pipe the output file to /dev/null, noting the size of the file that is printed when expand_dump completes its task. RETURN VALUES
Successful completion of the decompression. The user did not supply the correct number of command line arguments. The input file could not be read. The input file is not a compressed dump, or is corrupted. The output file could not be created or opened for writing and truncated. There was some problem writing to the output file (probably a full disk). The input file is not formated consistantly. It is probably corrupted. The input file could not be correctly decompressed. It is probably corrupted. EXAMPLES
expand_dump vmzcore.4 vmcore.4 SEE ALSO
Commands: dbx(1), kdbx(8), ladebug(1), savecore(8) Kernel Debugging System Administration expand_dump(8)

Featured Tech Videos