Skip to content

Reject a TTD launch with no trace specified (Fixes #910) - #1145

Open
xusheng6 wants to merge 1 commit into
devfrom
test_910_prompt_ttd_trace
Open

Reject a TTD launch with no trace specified (Fixes #910)#1145
xusheng6 wants to merge 1 commit into
devfrom
test_910_prompt_ttd_trace

Conversation

@xusheng6

@xusheng6 xusheng6 commented Jul 24, 2026

Copy link
Copy Markdown
Member

Fixes #910.

This PR fails the TTD launch attempt and gives a meaningful error message (rather than the cryptic OpenDumpFile failed with xxxxx)

The check are both added in the UI and the debug adapter

The TTD adapter replays a recorded trace, but nothing checked that one was
actually configured, so launching without a trace path failed deep inside the
engine with an opaque "OpenDumpFile failed: 0x..." HRESULT.

Validate the trace path in AdapterSettingsDialog::apply() and keep the dialog
open with an explanation instead of accepting it. The settings view writes each
value as it is edited, so the current value can simply be read back; no changes
to SettingsView are needed. The check is limited to the launch group with the
DBGENG_TTD adapter selected so the other flows are unaffected.

Also check the trace path in DbgEngTTDAdapter::ExecuteWithArgsInternal before
starting the engine, which covers the headless and scripted paths as well as
the launches where the settings dialog is skipped (#1133).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

prompt for trace when TTD backend selected

1 participant