From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb/breakpoint] Fix assert in jit_event_handler
Date: Mon, 24 May 2021 09:20:01 -0600 [thread overview]
Message-ID: <87wnrow44e.fsf@tromey.com> (raw)
In-Reply-To: <df106571-69d5-3d3a-8559-3b823ad9cd31@suse.de> (Tom de Vries's message of "Fri, 21 May 2021 13:27:55 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Simon> It's quite annoying that separate debug info files are represented by
Simon> "objfile"s...
Tom> Yeah, indeed.
Tom> And you could even say that that's fine, but question whether they
Tom> should be in the objfiles list, that is, have the default behaviour of:
I've long thought this was a design error, and that having the separate
debug objfile be replaced with supplementary BFDs attached to the main
objfile would be a better design.
If someone wants to implement this, I'm all for it.
Tom
prev parent reply other threads:[~2021-05-24 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 15:29 Tom de Vries
2021-05-20 16:22 ` Simon Marchi via Gdb-patches
2021-05-20 22:04 ` Tom de Vries
2021-05-21 19:12 ` Tom de Vries
2021-05-21 11:27 ` Tom de Vries
2021-05-21 14:07 ` Simon Marchi via Gdb-patches
2021-05-24 15:20 ` Tom Tromey [this message]
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=87wnrow44e.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