Missing some function and source file names.

[jha...@gmail.com]

When we run mindump_stackwalk on our dump files the output is missing some function and source file names for our modules.  To throw a number out there, say 50% of the function and source file names will show up for module "x" but the rest will be missing and we just get an address (50% is a bit arbitrary, it varies quite a bit).  

Reading the docs here:

https://code.google.com/p/google-breakpad/wiki/StackWalking#Getting_source_line_information

it sounds like there may be cases where this is expected, is that true or does it sound like we might have a problem somewhere?  I assume if there's a problem it is most likely when symbols are dumped.  I haven't noticed any errors when dumping symbols, but to be sure I would need to log the output and take a closer look.  It happens with all modules from our app (we currently don't have symbols for OS specific modules, which are also commonly present in our stack traces) and we see this with dumps from both Mac OS and Windows.    

Thanks for any info.

[Bruce Dawson]

Either you are not getting symbols at all for some modules, or you are getting symbols for those modules but the symbols are not complete. You need to figure out which it is.

 

The debug output from minidump_stackwalk tells you when symbols cannot be found. You can also manually look for .sym files to see if they exist, and if they don't then figure out why they aren't being created.

 

If the relevant .sym files exist then load them into a text editor and look to see whether the symbols are present. If the symbols you care about are missing then experiment with the process that creates .sym files to find out why not.

[jha...@gmail.com]

Thanks for the reply Bruce.  Looks like the .sym files are there and the function names that are missing are in them.  Once we added symbols for OS libraries our stack traces improved quite a bit.  We need to do some more testing with proper crashes, but that seems to be the issue at the moment.

[Bruce Dawson]

If you're trying to track down OS symbols then some of my blog posts from a few months ago may be useful. The most recent one (and easiest, when it works) is this one:

 

http://randomascii.wordpress.com/2013/03/05/symbols-on-linux-update-fedora-fixes/#more-1056

On Fri, Apr 26, 2013 at 4:36 PM, <jha...@gmail.com> wrote:

Thanks for the reply Bruce.  Looks like the .sym files are there and the function names that are missing are in them.  Once we added symbols for OS libraries our stack traces improved quite a bit.  We need to do some more testing with proper crashes, but that seems to be the issue at the moment.

--
You received this message because you are subscribed to a topic in the Google Groups "google-breakpad-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-breakpad-discuss/x-fp9JPrG9k/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to google-breakpad-d...@googlegroups.com.
To post to this group, send email to google-brea...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-breakpad-discuss?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.