feature request: breakpad dumps on windows should contain CLR stack information

[GoogleCodeExporter]

What steps will reproduce the problem?
1. create an application that mixes C# CLR code and c++ native code
2. initialize breakpad in c++ code
3. create an exception in the c++ code

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

the expected output is a dump file that contains both managed and native stacks.
instead breakpad creates dump files with native stacks but without any managed 
CLR stacks

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

breakpad r639 on windows server 2003

Please provide any additional information below.

Original issue reported on code.google.com by avia...@gmail.com on 14 Aug 2011 at 7:47

[GoogleCodeExporter]

Do you know how to do this without writing full memory dumps? I found this from 
googling around: http://www.debuginfo.com/tools/clrdump.html but it doesn't 
include source.

Original comment by ted.mielczarek on 31 Aug 2011 at 4:30

[GoogleCodeExporter]

our friends in microsoft knows how to do it, they provide a tool called CDB a 
console based debugger whose dumps contain both native and clr information. 
http://msdn.microsoft.com/en-us/windows/hardware/gg463009
unfortunately CDB doesnt contain source either. 

Original comment by avia...@gmail.com on 1 Sep 2011 at 9:15

[GoogleCodeExporter]

Okay, well, if you want to reverse-engineer that data, or find a reference for 
it, feel free. Seems hard to implement without any reference.

Original comment by ted.mielczarek on 11 Oct 2011 at 4:14

[GoogleCodeExporter]

I wrap a C++ instance ExceptionHandler, and my C# applications uses P/Invoke to 
initial the instance(out-of-process). I found Windows has much higher 
probability of notify "xxx has stopped working" in CLR environment. Thus 
ExceptionHandler did not capture the error. Can someone tell me some experience 
when use breakpad for C#.

Original comment by junrenzh...@gmail.com on 3 May 2013 at 5:18