From: Doug Evans <dje@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] find_partial_die cleanups
Date: Mon, 09 Apr 2012 18:26:00 -0000 [thread overview]
Message-ID: <CADPb22RR=1WudivMTEevxPnoi5G_vOawx7-t_wXcR8AmxfbHJQ@mail.gmail.com> (raw)
In-Reply-To: <87mx6k93f4.fsf@fleche.redhat.com>
On Mon, Apr 9, 2012 at 11:16 AM, Tom Tromey <tromey@redhat.com> wrote:
> Doug> + error (_("Dwarf Error: Type Unit at offset 0x%lx contains"
> Doug> + " external reference to offset 0x%lx [in module %s].\n"),
> Doug> + (long) cu->header.offset.sect_off, (long) offset.sect_off,
> Doug> + bfd_get_filename (objfile->obfd));
>
> Why an error and not a complaint?
>
> I ask because errors have a pretty drastic effect on debuginfo reading.
"Right on queue." :-)
Indeed. And I would have used a complaint but the callers aren't
expecting a NULL return and since there is ample precedent, I went
with error.
I'm happy to go throught all the callers and bubble up the
consequences, but my first pass at this gave me pause.
> Doug> + struct dwarf2_section_info* sec;
>
> Wrong "*" placement.
Heh, righto.
next prev parent reply other threads:[~2012-04-09 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 17:46 Doug Evans
2012-04-09 18:16 ` Tom Tromey
2012-04-09 18:26 ` Doug Evans [this message]
2012-04-09 18:48 ` Tom Tromey
2012-04-10 19:19 ` 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='CADPb22RR=1WudivMTEevxPnoi5G_vOawx7-t_wXcR8AmxfbHJQ@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