From: Jim Blandy <jimb@redhat.com>
To: Aidan Skinner <aidan@velvet.net>
Cc: Hilfinger@otisco.mckusick.com, ac131313@redhat.com,
drow@mvista.com, per@bothner.com, green@redhat.com,
muller@cerbere.u-.strasbg.fr, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add type support for Ada
Date: Wed, 02 Oct 2002 11:59:00 -0000 [thread overview]
Message-ID: <vt2heg4adhx.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <20021001041712.E8933@velvet.net>
Aidan Skinner <aidan@velvet.net> writes:
> Thanks for answering these Paul. :)
>
> > > It looks to me as if the string cleanup stuff is distinct from the
> > > fixed instance stuff. These should be submitted as separate patches.
> >
> > They definitely are logically separate changes.
>
> Yeah, I'll split and resubmit and probably take the opportunity to
> include some more string cleanup stuff, rather than just the bits that
> ada-* reference...
Thanks!
> > > Should base_type use the tortoise-and-hare algorithm to detect cycles?
> >
> > An interesting suggestion. However, there is at least one existing
> > place where GDB doesn't bother. Compare with the following (non-Ada-
>
> I think it's worthwhile doing here, and if it works nicely it can be
> stolen for other places. My next revision of this patch will include
> this.
Great.
> > Umm. Interesting questions. As I recall, I had the impression that
> > a self-referencing range type COULD occur legitimately, but given that was
>
> I think they can, but my current understanding of the gdb type system
> probably bears some resemblence to swiss cheese. ;)
>
> I'll experiment a bit with trying to create one and see what I can find.
>
> > 4 years ago, my memory could be faulty. I suspect these tests were simply
> > bullet-(or segfault)-proofing. Replacing the NULL check at least with
> > an error would probably be a worthy experiment.
>
> Sounds like a plan.
Super. I can't tell whether this was the intention in that code, but
I'd much rather see GDB throw an internal error when it finds
something bogus than return some handy plausible value.
next prev parent reply other threads:[~2002-10-02 18:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-25 20:00 Aidan Skinner
2002-09-26 19:24 ` Andrew Cagney
2002-09-27 13:08 ` Jim Blandy
2002-09-28 2:24 ` Paul N. Hilfinger
2002-09-30 20:17 ` Aidan Skinner
2002-10-02 11:59 ` Jim Blandy [this message]
2002-10-02 11:57 ` 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=vt2heg4adhx.fsf@zenia.red-bean.com \
--to=jimb@redhat.com \
--cc=Hilfinger@otisco.mckusick.com \
--cc=ac131313@redhat.com \
--cc=aidan@velvet.net \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=green@redhat.com \
--cc=muller@cerbere.u-.strasbg.fr \
--cc=per@bothner.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