Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sourceware.org
Subject: Re: C++ related core dump
Date: Thu, 17 Nov 2005 14:04:00 -0000	[thread overview]
Message-ID: <20051117140452.GB11432@nevyn.them.org> (raw)
In-Reply-To: <200511170945.jAH9jBle024772@elgar.sibelius.xs4all.nl>

On Thu, Nov 17, 2005 at 10:45:11AM +0100, Mark Kettenis wrote:
> No, no, you misread that bit above.  antennac is an instance of class
> ROScalarColumn<int>.  So antennac(0) *is* an invocation of operator().

Oh.  Then what type IS the fsym?

> > GDB does _not_ support calling constructors, though.  This is a bit
> > tricky.
> > 
> > > Regardless of properly invoking operator(), we should do something
> > > about this crash.  Can we do something better than the attached patch?
> > 
> > > -      func_name	= cp_func_name (qualified_name);
> > > +      if (qualified_name)
> > > +	func_name = cp_func_name (qualified_name);
> > 
> > Return earlier if fsym is not a function?  Or this seems reasonable, to
> > avoid the crash.
> 
> Hmm the comment just below mentions C-style functions.  Doesn't
> SYMBOL_CPLUS_DEMANGLED_NAME (fsym) return NULL for C-style functions
> too?  In that case I think my patch is indeed the right approach.

Probably so, but let's work out what's going on first.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-11-17 14:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15 10:15 Mark Kettenis
2005-11-17  4:11 ` Daniel Jacobowitz
2005-11-17  9:46   ` Mark Kettenis
2005-11-17 14:04     ` Daniel Jacobowitz [this message]
2005-11-22  9:21       ` Mark Kettenis
2005-11-22 14:01         ` 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=20051117140452.GB11432@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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