Breakpad captures incorrect dmp when threads contain lambdas introduced in c++ 11.

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Do not know of an exact repro but most of the time when the stack trace 
contains lambda calls, the stack turns out to be incorrect.
1 specific scenario was when a function that was just a stub was showing up in 
the stack trace at frame 10 which is not possible as the function is just a 
no-op.

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

What version of the product are you using? On what operating system?
Breakpad revision: r1348 Android OS: 4.4

Please provide any additional information below.

Original issue reported on code.google.com by atishayj...@gmail.com on 12 Sep 2014 at 7:47

GoogleCodeExporter commented 9 years ago

My best guess would be that we're not dumping the symbols correctly. If you 
could provide a reduced testcase that'd be helpful. Perhaps a simple example 
that calls a lambda that calls abort()?

Original comment by ted.mielczarek on 12 Sep 2014 at 4:16

GoogleCodeExporter commented 9 years ago

My best guess would be that we're not dumping the symbols correctly. If you 
could provide a reduced testcase that'd be helpful. Perhaps a simple example 
that calls a lambda that calls abort()?

Original comment by ted.mielczarek on 12 Sep 2014 at 4:17

koying / google-breakpad

Breakpad captures incorrect dmp when threads contain lambdas introduced in c++ 11. #605