Suppress handler thread from appearing in MinidumpProcessor's ProcessState

[GoogleCodeExporter]

#34 changed the Windows client handler code to cause all minidumps to be
written by a dedicated handler thread.  We don't want that thread to show
up in the ProcessState returned by MinidumpProcessor, because it's not
really a legitimate state.

In #57, I'll add something to the minidump that indicates which thread the
handler thread was.  I'll also add something to indicate which thread
requested the dump to be written, even if the dump was not produced as a
result of a crash.

In this bug, I'll add support to the Minidump classes and MinidumpProcessor
to properly understand this information, and to prevent the CallStack from
the handler thread from showing up in the ProcessState.

Original issue reported on code.google.com by mmento...@gmail.com on 31 Oct 2006 at 4:58

[GoogleCodeExporter]

Original comment by mmento...@gmail.com on 31 Oct 2006 at 11:23

Attachments:

• airbag.65.1.patch

[GoogleCodeExporter]

Updated test data

Original comment by mmento...@gmail.com on 31 Oct 2006 at 11:24

Attachments:

• airbag.65-testdata.1.tar.bz2

[GoogleCodeExporter]

v2 addresses review comments

Original comment by mmento...@gmail.com on 6 Nov 2006 at 10:04

Attachments:

• airbag.65.2.patch

[GoogleCodeExporter]

v2 test data

Original comment by mmento...@gmail.com on 6 Nov 2006 at 10:04

Attachments:

• airbag.65-testdata.2.tar.bz2

[GoogleCodeExporter]

Checked in, revision [62].

Original comment by mmento...@gmail.com on 6 Nov 2006 at 11:01

• Changed state: Fixed