From: Doug Evans <dje@google.com>
To: gdb-patches <gdb-patches@sourceware.org>, Tom Tromey <tromey@redhat.com>
Subject: Re: [RFC] gdb_bfd_count_sections snafu
Date: Wed, 17 Apr 2013 15:10:00 -0000 [thread overview]
Message-ID: <CADPb22Q2ALdsLqSKUNZvJW31Yxx2-n4W91j0Yw7qQfNFj7fy4w@mail.gmail.com> (raw)
In-Reply-To: <yjt2ehe9r31a.fsf@ruffy2.mtv.corp.google.com>
On Wed, Apr 17, 2013 at 1:10 AM, Doug Evans <dje@google.com> wrote:
> [...]
> My preference would be code changes to remove the possibility
> for picking the wrong one, but that would, I think, be non-trivial.
Well, for completeness sake,
another thing we can do is add more asserts to catch the wrong
num_sections value being used.
next prev parent reply other threads:[~2013-04-17 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 14:55 Doug Evans
2013-04-17 15:10 ` Doug Evans [this message]
2013-04-27 18:55 ` Tom Tromey
2013-05-04 6:21 ` Doug Evans
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=CADPb22Q2ALdsLqSKUNZvJW31Yxx2-n4W91j0Yw7qQfNFj7fy4w@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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