search

gohome1984 / google-breakpad

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

SendAndExit is not unprotecting memory #315

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create a simple application that uses has a null pointer dereference
2. Crash the application
3. Notice breakpad catching the crash and then the Apple crash reporter 
catching the breakpad 
crash.

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

Expected breakpad to catch the crash, but both the breakpad reporter and the 
Apple Crash 
Reporter come up. 

Please use labels and text to provide additional information.

Here is a stack trace:

#0  0x0008fda1 in google_breakpad::ExceptionHandler::UninstallHandler at 
exception_handler.cc:599
#1  0x000919b5 in google_breakpad::ExceptionHandler::WaitForMessage at 
exception_handler.cc:513
#2  0x967c3095 in _pthread_start
#3  0x967c2f52 in thread_start

Original issue reported on code.google.com by preston....@gmail.com on 28 Apr 2009 at 9:55

GoogleCodeExporter commented 9 years ago 
Also, if I use the following command

defaults read NSGlobalDomain GoogleBreakpadSendAndExit

the result is 0

if I delete the GoogleBreakpadSendAndExit setting, the crash goes away

Original comment by preston....@gmail.com on 28 Apr 2009 at 9:56