diff options
| author | Tom Tromey <tromey@adacore.com> | 2023-09-05 06:55:54 -0600 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2023-09-12 10:31:26 -0600 |
| commit | f8ab027008863bd06513053ea9f84e1116c1cf73 (patch) | |
| tree | 628e1cb3b83a5d9c9e0b5b3165fff319be75e768 /gdb/stack.c | |
| parent | d1722abe60ca7c330210aa97c8ec52ff98644206 (diff) | |
| download | gdb-f8ab027008863bd06513053ea9f84e1116c1cf73.zip gdb-f8ab027008863bd06513053ea9f84e1116c1cf73.tar.gz gdb-f8ab027008863bd06513053ea9f84e1116c1cf73.tar.bz2 | |
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
Diffstat (limited to 'gdb/stack.c')
0 files changed, 0 insertions, 0 deletions