diff options
| author | Tom Tromey <tromey@adacore.com> | 2023-05-19 09:00:52 -0600 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2023-06-12 12:10:15 -0600 |
| commit | 7cb909c4091c156a8242f799e18af57d702da560 (patch) | |
| tree | b7621aa9ed2cca20a509f0baca1678ab455e541f /gdb/python/python-internal.h | |
| parent | 3c453cfb1945eb97f68b3aca4d84f4884c564d0c (diff) | |
| download | gdb-7cb909c4091c156a8242f799e18af57d702da560.zip gdb-7cb909c4091c156a8242f799e18af57d702da560.tar.gz gdb-7cb909c4091c156a8242f799e18af57d702da560.tar.bz2 | |
Do not report totalFrames from DAP stackTrace request
Currently, gdb will unwind the entire stack in response to the
stackTrace request. I had erroneously thought that the totalFrames
attribute was required in the response. However, the spec says:
If omitted or if `totalFrames` is larger than the available
frames, a client is expected to request frames until a request
returns less frames than requested (which indicates the end of the
stack).
This patch removes this from the response in order to improve
performance when the stack trace is very long.
Diffstat (limited to 'gdb/python/python-internal.h')
0 files changed, 0 insertions, 0 deletions