Open GoogleCodeExporter opened 9 years ago
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.
Original comment by shess@chromium.org
on 2 Sep 2009 at 7:52
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.
Original comment by jimbla...@gmail.com
on 2 Sep 2009 at 8:04
http://code.google.com/p/google-breakpad/issues/detail?id=333 it is!
Original comment by shess@chromium.org
on 2 Sep 2009 at 9:20
Original issue reported on code.google.com by
jeremy@chromium.org
on 1 Sep 2009 at 7:33