[Bug dap/34133] Crash when specifying --interpreter=dap and using the `attach` command while in an extended remote context.

https://sourceware.org/bugzilla/show_bug.cgi?id=3D34133

--- Comment #13 from Cynthia Thayer <cynthia.thayer at pm dot me> ---
(In reply to Tom Tromey from comment #11)
> (In reply to Cynthia Thayer from comment #3)
> > Hi Tom,
> >=20
> > The monitor command is a custom command for the Black Magic Probe I'm u=
sing,
> > its a multi target arm cortex debugger. swdp_scan requests that the pro=
be
> > scans for the presence of a target, then displays all present targets.
>=20
> Is the monitor command a necessary part of the startup here?
> Like, if I modify the DAP code to extend the attach sequence, is
> it necessary to allow for this?  Or is it something that can be
> sent later by the DAP client, and I don't need to allow it
> specifically in the middle of the "attach" request?

Yes, the probe requires, at a minimum, the `monitor swdp_scan` command in o=
rder
to initialize the debugger line and find devices, prior to the attach. After
attaching though, there is no reason to run any additional monitor commands.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=