Issue 332 in google-breakpad: More information for crashes in Cocoa functions

[codesite...@google.com]

Status: New
Owner: ----

New issue 332 by jer...@chromium.org: More information for crashes in Cocoa
functions
http://code.google.com/p/google-breakpad/issues/detail?id=332

For the Mac version of breakpad it would be very helpful if we could get the
following information included in the crash dumps:
* In the case of a crash in
___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___ can we record some
information about the exception in the crash dump?
* In the case of a crash in objc_msgSend can we record the name of the
selector that's being invoked.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Comment #1 on issue 332 by sh...@chromium.org: More information for crashes

in Cocoa functions
http://code.google.com/p/google-breakpad/issues/detail?id=332

While we're wishlisting, it would be useful if the stack trace contained
the name of the object's class in
addition to the name of the class the method is implemented in. We get a
number of crashes where the stack
trace is all Cocoa classes, it would be useful to know if these were
actually the inherited Cocoa methods in our
special sub-classes or not.

For example, a random trace:
0x9295c688 [libobjc.A.dylib + 0x00015688] objc_msgSend
0x91317dcb [AppKit + 0x00111dcb] -[NSControl sendAction:to:]
0x91317c51 [AppKit + 0x00111c51] -[NSCell _sendActionFrom:]
0x913172aa [AppKit + 0x001112aa] -[NSCell
trackMouse:inRect:ofView:untilMouseUp:]
0x91316afd [AppKit + 0x00110afd] -[NSButtonCell
trackMouse:inRect:ofView:untilMouseUp:]
0x913163b7 [AppKit + 0x001103b7] -[NSControl mouseDown:]
0x91314af6 [AppKit + 0x0010eaf6] -[NSWindow sendEvent:]
0x912e16a4 [AppKit + 0x000db6a4] -[NSApplication sendEvent:]
0x9123efe6 [AppKit + 0x00038fe6] -[NSApplication run]

Knowing that the NSWindow in question was actually an OurMagicPopupWindow
would be super helpful.

[codesite...@google.com]

Comment #2 on issue 332 by jimblandy: More information for crashes in Cocoa
functions
http://code.google.com/p/google-breakpad/issues/detail?id=332

That sounds helpful to me too, but:

Please submit each wish as a separate issue. Adding it here makes it hard
to keep
track of progress and decisions.

[codesite...@google.com]

Comment #3 on issue 332 by sh...@chromium.org: More information for crashes

in Cocoa functions
http://code.google.com/p/google-breakpad/issues/detail?id=332

http://code.google.com/p/google-breakpad/issues/detail?id=333 it is!