diff options
| author | Tom de Vries <tdevries@suse.de> | 2022-10-19 17:41:47 +0200 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2022-10-19 17:41:47 +0200 |
| commit | 508ccf9b3e1db355037a4a1c9004efe0d6d3ffbf (patch) | |
| tree | d03bd125007dccd265f932e9ee6ab367bd8550c9 /gdb/testsuite/gdb.python/py-lazy-string.c | |
| parent | f34652de0b68c4ee3050828b43a2839b852b5821 (diff) | |
| download | binutils-508ccf9b3e1db355037a4a1c9004efe0d6d3ffbf.zip binutils-508ccf9b3e1db355037a4a1c9004efe0d6d3ffbf.tar.gz binutils-508ccf9b3e1db355037a4a1c9004efe0d6d3ffbf.tar.bz2 | |
[gdb] Fix assert in handle_jit_event
With the cc-with-tweaks.sh patch submitted here (
https://sourceware.org/pipermail/gdb-patches/2022-October/192586.html ) we run
with:
...
$ export STRIP_ARGS_STRIP_DEBUG=--strip-all
$ make check RUNTESTFLAGS="gdb.base/jit-reader.exp \
--target_board cc-with-gnu-debuglink"
...
into the following assert:
...
(gdb) run ^M
Starting program: jit-reader ^M
gdb/jit.c:1247: internal-error: jit_event_handler: \
Assertion `jiter->jiter_data != nullptr' failed.^M
...
Fix this by handling the
jit_bp_sym.objfile->separate_debug_objfile_backlink != nullptr case in
handle_jit_event.
Tested on x86_64-linux.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29277
Diffstat (limited to 'gdb/testsuite/gdb.python/py-lazy-string.c')
0 files changed, 0 insertions, 0 deletions