diff options
author | Tom de Vries <tdevries@suse.de> | 2021-02-05 17:47:07 +0100 |
---|---|---|
committer | Tom de Vries <tdevries@suse.de> | 2021-02-05 17:47:07 +0100 |
commit | 7c6944ab9bc4fd6e641c59f7c78ca4e1ec78fe7e (patch) | |
tree | 763a574f3d9807001063d180b6282de956f1900e /gnulib/import/m4/memchr.m4 | |
parent | e77b0004dd114d6ddf3bb92b521b2854341f3f85 (diff) | |
download | fsf-binutils-gdb-7c6944ab9bc4fd6e641c59f7c78ca4e1ec78fe7e.zip fsf-binutils-gdb-7c6944ab9bc4fd6e641c59f7c78ca4e1ec78fe7e.tar.gz fsf-binutils-gdb-7c6944ab9bc4fd6e641c59f7c78ca4e1ec78fe7e.tar.bz2 |
[gdb/breakpoints] Handle glibc with debuginfo in create_exception_master_breakpoint
The test-case nextoverthrow.exp is failing on targets with unstripped libc.
This is a regression since commit 1940319c0ef "[gdb] Fix internal-error in
process_event_stop_test".
The problem is that this code in create_exception_master_breakpoint:
...
for (objfile *sepdebug = obj->separate_debug_objfile;
sepdebug != nullptr; sepdebug = sepdebug->separate_debug_objfile)
if (create_exception_master_breakpoint_hook (sepdebug))
...
iterates over all the separate debug object files, but fails to handle the
case that obj itself has the debug info we're looking for.
Fix this by using the separate_debug_objfiles () range instead, which does
iterate both over obj and the obj->separate_debug_objfile chain.
Tested on x86_64-linux.
gdb/ChangeLog:
2021-02-05 Tom de Vries <tdevries@suse.de>
PR breakpoints/27330
* breakpoint.c (create_exception_master_breakpoint): Handle case that
glibc object file has debug info.
Diffstat (limited to 'gnulib/import/m4/memchr.m4')
0 files changed, 0 insertions, 0 deletions