From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: PATCH to gnuv3_rtti_type
Date: Wed, 17 Apr 2002 19:07:00 -0000 [thread overview]
Message-ID: <20020417220806.A22040@nevyn.them.org> (raw)
In-Reply-To: <wvl8z7llq6b.fsf@prospero.cambridge.redhat.com>
On Thu, Apr 18, 2002 at 03:02:36AM +0100, Jason Merrill wrote:
> gnuv3_rtti_type still gets confused sometimes, by constructor vtables and
> namespaces at least. This wouldn't be a big problem, as mostly I don't
> care what the real type is, except that it gives an error and aborts. If
> I'm just trying to print the contents of a pointer, this is rather
> annoying.
>
> This patch changes the errors to warnings, so that I get the normal output
> which is all I really care about.
>
> OK?
Sure, thank you.
> 2002-04-14 Jason Merrill <jason@redhat.com>
>
> * gnu-v3-abi.c (gnuv3_rtti_type): If we get confused, just warn
> and return NULL.
>
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-04-18 2:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 19:02 Jason Merrill
2002-04-17 19:07 ` Daniel Jacobowitz [this message]
2002-04-30 11:28 ` Jason Merrill
2002-04-30 12:10 ` Michael Snyder
2002-05-03 12:36 ` Jason Merrill
2002-05-03 14:16 ` Daniel Jacobowitz
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=20020417220806.A22040@nevyn.them.org \
--to=drow@mvista.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