search

wukenaihe / google-breakpad

Automatically exported from code.google.com/p/google-breakpad
0 stars 0 forks source link

breakpad doesn't provide versions for loaded libraries on Mac OS X #181

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Compare a crash report from Mac OS X and Win32, e.g.
https://crash-reports.mozilla.com/reports/report/index/b18c5405-0c84-11dc-949e-0
01a4bd43ed6
and
https://crash-reports.mozilla.com/reports/report/index/0aaab7f8-0ca1-11dc-a967-0
01a4bd43ef6

What is the expected output? What do you see instead?

Loaded libraries have version info on Win32 but not on Mac OS X.

What version of the product are you using? On what operating system?

rev 174 as landed in Mozilla.org cvs

Please provide any additional information below.

luser mentioned on irc that breakpad does provide this info on Win32 but
not on Mac OS X.

Original issue reported on code.google.com by smokey.ardisson@gmail.com on 28 May 2007 at 2:46

GoogleCodeExporter commented 9 years ago 
Do macho sharedlibs have version numbers at all? I don't think the concept 
applies.

Original comment by bsmedb...@gmail.com on 29 May 2007 at 2:27

GoogleCodeExporter commented 9 years ago 
Some do, some don't ("loaded libraries" is perhaps not the right term); see the
attached section of the last part of a Mac OS X crash log.

I'm primarily interested in versions from third-party 
libraries/frameworks/plugins
that are loaded, e.g. Flash, JEP, haxies, as that makes it easy to check whether
someone is using an older version with known bugs/crashes/incompatibilities.  
That
makes it easy to screen crashes, find patterns, and, in Mozilla, potentially 
email
the crashee and see if the issue goes away if they upgrade to the current 
version.

Original comment by smokey.ardisson@gmail.com on 1 Jun 2007 at 3:58

Attachments:

GoogleCodeExporter commented 9 years ago 
We should fix this.

Original comment by mmento...@gmail.com on 24 Oct 2007 at 4:24

GoogleCodeExporter commented 9 years ago 
The attached patch is a fix for this

Original comment by neal...@gmail.com on 15 Oct 2008 at 10:09

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by neal...@gmail.com on 10 Feb 2009 at 9:16