From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] print arrays with indexes
Date: Mon, 03 Oct 2005 15:50:00 -0000 [thread overview]
Message-ID: <20051003155019.GA23854@nevyn.them.org> (raw)
In-Reply-To: <20051003061733.GL938@adacore.com>
On Sun, Oct 02, 2005 at 11:17:33PM -0700, Joel Brobecker wrote:
> > Should the "return 0;" cases in get_array_low_bound be errors? Or even
> > internal errors (probably not)?
>
> I don't think we should use an internal error in this case, since the
> erroneous situation can also come from incorrect debugging information.
> In this case, it would be misleading to label this as an internal error
> when the problem is outside the debugger.
>
> I wouldn't use an error in this case either, as it allows us to emit
> a warning instead, and recover in a way that at least allows us to
> print the array. Otherwise, it's more complicated to still print the
> array.
>
> So I would leave this unchanged. Or perhaps a little comment addition
> before the function, along with the description, explaining the above?
A comment would be nice. With that change, the patch (and testcase and
docs) are OK.
> > There's already lots of code that uses TYPE_LOW_BOUND (TYPE_INDEX_TYPE
> > (array_type)). If that's not valid, we need to know why not.
>
> The new function does essentially this, except that it adds a bit
> of double-checking, probably to avoid falling in a trap laid by
> incorrect debugging information.
Nick was recently writing some code that needed the bounds of an array.
We found three or four different idioms for finding this used
throughout the GDB source. Figuring out which ones are right and which
ones are obsolete is a royal pain. That's my only concern here.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-10-03 15:50 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 20:20 [RFC/RFA] " Joel Brobecker
2005-09-06 20:57 ` Daniel Jacobowitz
2005-09-07 5:40 ` Joel Brobecker
2005-09-07 13:23 ` Daniel Jacobowitz
2005-09-07 20:24 ` Joel Brobecker
2005-09-14 17:13 ` [RFA] " Joel Brobecker
2005-09-17 20:49 ` Daniel Jacobowitz
2005-09-17 21:51 ` Joel Brobecker
2005-09-17 22:07 ` Daniel Jacobowitz
2005-09-18 3:37 ` Eli Zaretskii
2005-09-18 3:46 ` Daniel Jacobowitz
2005-09-18 5:41 ` Joel Brobecker
2005-09-18 19:08 ` Eli Zaretskii
2005-09-18 19:19 ` Daniel Jacobowitz
2005-09-18 20:05 ` Eli Zaretskii
2005-09-20 7:31 ` Joel Brobecker
2005-09-20 19:18 ` Eli Zaretskii
2005-09-20 19:31 ` Joel Brobecker
2005-09-20 19:33 ` Daniel Jacobowitz
2005-09-20 19:39 ` Joel Brobecker
2005-09-21 3:44 ` Eli Zaretskii
2005-09-22 16:47 ` Joel Brobecker
2005-09-26 1:23 ` Daniel Jacobowitz
2005-09-27 1:04 ` Joel Brobecker
2005-10-02 22:42 ` Daniel Jacobowitz
2005-10-03 6:17 ` Joel Brobecker
2005-10-03 15:50 ` Daniel Jacobowitz [this message]
2005-10-03 21:23 ` Joel Brobecker
2005-10-04 7:02 ` Joel Brobecker
2005-10-04 7:41 ` Joel Brobecker
2005-09-21 3:44 ` Eli Zaretskii
2005-09-18 8:53 ` Mark Kettenis
2005-09-18 19:10 ` Eli Zaretskii
2005-09-07 20:39 ` [RFC/RFA] " Jim Blandy
2005-09-07 21:41 ` Joel Brobecker
2005-09-09 19:14 ` Jim Blandy
2005-09-06 21:45 ` Jim Blandy
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=20051003155019.GA23854@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.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