From: Daniel Jacobowitz <drow@mvista.com>
To: Per Bothner <per@bothner.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: patch to robustify gnuv3_rtti_type
Date: Sat, 19 Jan 2002 17:50:00 -0000 [thread overview]
Message-ID: <20020119205040.A4069@nevyn.them.org> (raw)
In-Reply-To: <3C49D9DF.4040700@bothner.com>
On Sat, Jan 19, 2002 at 12:41:03PM -0800, Per Bothner wrote:
> Ok to check in? This doesn't fix the real problem, which is that
> gcj produces vtables that aren't properly abi-compliant. Hopefully,
> we'll fix that. But for now, let's at least prevent gdb from crashing.
By the way, with current GDB and gjc 3.0.3, I see a stabs debugging bug
that I mean to fix and a collection of assorted DWARF2 bugs. I'll be
poking at these soon.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-01-20 1:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-19 12:40 Per Bothner
2002-01-19 15:38 ` Daniel Jacobowitz
2002-01-19 16:15 ` Per Bothner
2002-01-19 16:19 ` Daniel Jacobowitz
2002-01-20 12:43 ` Per Bothner
2002-01-20 12:54 ` Daniel Jacobowitz
2002-01-20 16:00 ` Per Bothner
2002-01-20 14:24 ` Daniel Berlin
2002-01-19 17:50 ` Daniel Jacobowitz [this message]
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=20020119205040.A4069@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--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