diff options
| author | Jon Turney <jon.turney@dronecode.org.uk> | 2017-03-11 19:02:43 +0000 |
|---|---|---|
| committer | Mike Frysinger <vapier@chromium.org> | 2017-03-11 20:58:29 +0000 |
| commit | 7ec3caf6c7cdff0a99cd34249acfdc61f76f2d86 (patch) | |
| tree | eb1232692b20172ccb4116ae7c86c7209a39f429 /src/google_breakpad/common/minidump_cpu_mips.h | |
| parent | iOS client identifies itself via URL params (diff) | |
| download | breakpad-7ec3caf6c7cdff0a99cd34249acfdc61f76f2d86.tar.xz | |
Fix Windows client ExceptionHandlerTest tests
ExceptionHandlerTest.InvalidParameterMiniDumpTest and
ExceptionHandlerTest.PureVirtualCallMiniDumpTest both also exercise a
feature that if the MiniDumpWithFullMemory MINIDUMP_TYPE is used, both
UUID.dmp and UUID-full.dmp files are written.
This is currently broken, and requesting a minidump with
MiniDumpWithFullMemory MINIDUMP_TYPE fails, as the file handle for the full
dump is not set.
Call GenerateFullDumpFile() if MiniDumpWithFullMemory is requested, to
generate a filename for the full dump file and set the file handle.
Currently GenerateFullDumpFile() also generates another UUID for the full
dump filename, so also make the private method
MinidumpGenerator::GenerateDumpFilePath() idempotent (so the same UUID is
reused)
(Note that calling Generate(|Full)DumpFile() more than once is not
permitted, so there's no behaviour where this changed the UUID to preserve)
BUG=
Change-Id: I74304f38b398f53da1c24f368dedfba8463da9e5
Reviewed-on: https://chromium-review.googlesource.com/452978
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Diffstat (limited to 'src/google_breakpad/common/minidump_cpu_mips.h')
0 files changed, 0 insertions, 0 deletions