Tom Tromey f8ab027008 Avoid spurious breakpoint-setting failure in DAP ...

A user pointed out that if a DAP setBreakpoints request has a 'source'
field in a SourceBreakpoint object, then the gdb DAP implementation
will throw an exception.

While SourceBreakpoint does not allow 'source' in the spec, it seems
better to me to accept it.  I don't think we should fully go down the
"Postel's Law" path -- after all, we have the type-checker -- but at
the same time, if we do send errors, they should be intentional and
not artifacts of the implementation.

Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30820

2023-09-12 10:31:26 -06:00

..

command

…

dap

Avoid spurious breakpoint-setting failure in DAP

2023-09-12 10:31:26 -06:00

function

…

printer

…

__init__.py

Restore previous sigmask in gdb.block_signals

2023-07-31 06:35:32 -06:00

disassembler.py

…

FrameDecorator.py

Use frame.name() in FrameDecorator

2023-08-03 09:35:38 -06:00

FrameIterator.py

…

frames.py

Full paths in DAP stackTrace responses

2023-08-01 12:52:26 -06:00

printing.py

Handle array- and string-like values in no-op pretty printers

2023-09-05 11:10:24 -06:00

prompt.py

…

styling.py

…

types.py

…

unwinder.py

…

xmethod.py

…