Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Add a little IBM XL C++ specific code in dwarf2read.c, to set TYPE_VPTR_FIELDNO and TYPE_VPTR_BASETYPE of a virtual class correctly
Date: Tue, 31 May 2005 05:46:00 -0000	[thread overview]
Message-ID: <20050531025031.GA7983@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0504301332010.26869@plinuxt18.cn.ibm.com>

Your computer's date is wrong; please fix that.  I had to go hunting to
see where this message was filed :-)

On Sat, Apr 30, 2005 at 01:53:46PM -0700, Wu Zhou wrote:
> Daniel, 
> 
> As we discussed in a previous thread before, gdb will drop into SEGV
> fault when handling the debug-info of a virtual class which has no
> DW_AT_containing_type attribute.  ARM's RVCT compiler will generate 
> this kind of debuginfo and prone to trigger SEGV error, which you 
> fixed in a big un-cleanuped patch.  IBM's XL compiler will also 
> generate this kind of debuginfo and prone to SEGV error too, on 
> which I posted a small patch based on yours.  
> 
> I see that you are still too busy to look into this.  But maybe we
> could handle this somewhat easily.  My thought is to begin with 
> eliminating the SEGV error first, which only need a small fix.  Then
> we could go on with other parts.  So I post the following IBM XLC++ 
> specific patch, wishing that we could make some progress on this. 
> What is your point on this idea?  If you think it is ok, I could also
> add ARM specific code into this patch.  Please review and comment. 
> Thanks a lot!

I am not the maintainer of this code, so I can't approve patches to it.  
You currently need to speak with Elena about DWARF-2 patches.

I think the change is probably reasonable.  Alternatively, we could
teach GDB not to rely on TYPE_VPTR_FIELDNO and TYPE_VPTR_BASETYPE if
the C++ ABI in use does not require them, which the GNU v3 ABI does
not.  That would also be a good solution.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-05-31  2:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-31  3:31 Wu Zhou
2005-05-31  5:46 ` Daniel Jacobowitz [this message]
2005-05-31 13:27   ` Wu Zhou
2005-06-13  3:26     ` 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=20050531025031.GA7983@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=woodzltc@cn.ibm.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