diff options
| author | Jeremy Morse <jeremy.morse@sony.com> | 2020-02-13 12:43:28 +0000 |
|---|---|---|
| committer | Jeremy Morse <jeremy.morse@sony.com> | 2020-02-13 12:46:32 +0000 |
| commit | 26f6aa9e3ba47c5ccb9d837310b59a5087549b7d (patch) | |
| tree | c8acdf6fe2939c0e47c593358938b64fe98bb88e /lldb/packages/Python/lldbsuite/test/configuration.py | |
| parent | b1309a18ba7314332cf05a40f48db4d42a51f214 (diff) | |
| download | llvm-26f6aa9e3ba47c5ccb9d837310b59a5087549b7d.zip llvm-26f6aa9e3ba47c5ccb9d837310b59a5087549b7d.tar.gz llvm-26f6aa9e3ba47c5ccb9d837310b59a5087549b7d.tar.bz2 | |
[debuginfo-tests] Fix Dexter process creation failure on Windows
When writing the Windows dbgeng driver for Dexter, I couldn't work out why it
would either launch a process and leave it free running, or if I started the
process suspended, never do anything with it. The result was a hack to create
and attach processes manually. This has been flaking out on Reids Windows
buildbot, and clearly wasn't a good solution.
Digging into this, it turns out that the "normal" cdb / windbg behaviour of
breaking whenever we attach to a process is not the default: it has to be
explicitly requested from the debug engine. This patch does so (by setting
DEBUG_ENGOPT_INITIAL_BREAK in the engine options), after which we can simply
call "CreateProcessAndAttach2" and everything automagically works.
No test for this behaviour: everything was just broken before.
Differential Revision: https://reviews.llvm.org/D74409
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/configuration.py')
0 files changed, 0 insertions, 0 deletions