Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Craig Rodrigues <rodrigc@attbi.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb 5.1.92-1 crash on C++ program
Date: Thu, 02 May 2002 14:11:00 -0000	[thread overview]
Message-ID: <20020502211146.GB25410@nevyn.them.org> (raw)
In-Reply-To: <20020502170018.A31253@attbi.com>

On Thu, May 02, 2002 at 05:00:18PM -0400, Craig Rodrigues wrote:
> The static trace for gdb looked like:
> 
> #0  0x080a77bd in fill_in_vptr_fieldno ()
> #1  0x080a77f2 in fill_in_vptr_fieldno ()
> #2  0x080a77f2 in fill_in_vptr_fieldno ()

This strongly suggests that a type appears in its own TYPE_BASECLASS
list.  Could you provide a small testcase - probably only the necessary
types to define the object that caused the segfault will suffice.  This
might even be related to the stabs bug Jim just fixed.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2002-05-02 21:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-02 14:00 Craig Rodrigues
2002-05-02 14:11 ` 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=20020502211146.GB25410@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=rodrigc@attbi.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