From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/breakpoints] Fix longjmp master breakpoint with separate debug info
Date: Wed, 27 Jan 2021 14:37:09 -0700 [thread overview]
Message-ID: <87v9bidptm.fsf@tromey.com> (raw)
In-Reply-To: <20210127143115.GA11549@delia> (Tom de Vries's message of "Wed, 27 Jan 2021 15:31:17 +0100")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> 2021-01-27 Tom de Vries <tdevries@suse.de>
Tom> PR breakpoints/27205
Tom> * breakpoint.c (create_longjmp_master_breakpoint_probe)
Tom> (create_longjmp_master_breakpoint_names): New function, factored out
Tom> of ...
Tom> (create_longjmp_master_breakpoint): ... here. Only try to install
Tom> longjmp_names breakpoints in libc.so/libc.so.debug if installing probe
Tom> breakpoint in libc.so failed.
This looks reasonable to me. Thanks for doing it.
Tom> + /* Skip separate debug object. */
Tom> + if (obj->separate_debug_objfile_backlink)
Normally this would be written != nullptr.
Tom> + /* Iterate over separate debug objects and try longjmp_names
Tom> + kind breakpoints. */
Tom> + for (objfile *sepdebug = obj->separate_debug_objfile;
Tom> + sepdebug != nullptr; sepdebug = sepdebug->separate_debug_objfile)
Tom> + if (create_longjmp_master_breakpoint_names (sepdebug))
Tom> + break;
I guess this can't use separate_debug_iterator / separate_debug_range
since that returns the parent objfile first.
Tom
next prev parent reply other threads:[~2021-01-27 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 14:31 Tom de Vries
2021-01-27 21:37 ` Tom Tromey [this message]
2021-01-28 9:55 ` Tom de Vries
2021-01-28 20:07 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9bidptm.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox