public inbox for
 help / color / mirror / Atom feed
From: Nathan Sidwell <>
To: Gary Benson <>,
Cc: Carlos O'Donell <>,
Subject: Re: infinity notes
Date: Fri, 02 Dec 2016 12:55:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20161201113300.GA10328@blade.nx>


> I also appreciate that there are other users who would be unhappy
> if they had to install debuginfo where they didn't before.  I'm
> trying to balance everyone's needs with this.

Yeah, I can see that's a challenge.

> into separated debuginfo.  Its also possible to imagine that different
> notes could go in different places in the same build, so you could
> have very debugger-specific notes like pretty-printer accessors in
> debuginfo, and more general purpose notes like the thread debug ones
> unstripped.

That flexibility is good.  It might be wise to document it early on with 
an example design at least -- so that those who add additional 
functionality don't blindly add new NOTES segments.

> The "unknown note #5" you saw at Cauldron will go away once tools
> are updated to recognise the notes.  I have patches ready to go for
> binutils, and I'll likely update elfutils too once everything's
> more fixed.

Right.  My point was that someone without an updated tool might be more 
informed. (Hey, if you have users who don't want debug info, I'll have 
ones that have old tools!)

Anyway, it seems like you're thinking about the issue, which is great!


Nathan Sidwell

      parent reply	other threads:[~2016-12-02 12:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2016-12-01 11:33 ` Gary Benson
2016-12-01 13:26   ` Carlos O'Donell
2016-12-02 12:55   ` Nathan Sidwell [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).