From: Daniel Jacobowitz <drow@false.org>
To: "André Pönitz" <apoenitz@trolltech.com>
Cc: gdb@sourceware.org
Subject: Re: problem with gdb's 'call'
Date: Tue, 12 Aug 2008 22:51:00 -0000 [thread overview]
Message-ID: <20080812153015.GA8546@caradoc.them.org> (raw)
In-Reply-To: <200808121727.40394.apoenitz@trolltech.com>
On Tue, Aug 12, 2008 at 05:27:39PM +0200, André Pönitz wrote:
> > > Is there a way to make the gdb core accept the mangled name without
> > > attempting to demangling it (to avoid the crash)?
> >
> > The crash has nothing to do with demangling, but you can disable
> > overload resolution and that should help. "set overload-resolution
> > off".
>
> Is there somewhere a description in what code paths setting variables
> like overload-resolution or demangle-style has an effect?
Just the description of the commands in the manual.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-08-12 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 15:30 André Pönitz
2008-08-12 16:12 ` Daniel Jacobowitz
2008-08-12 21:10 ` André Pönitz
2008-08-12 22:51 ` Daniel Jacobowitz [this message]
2008-08-12 19:30 ` Andreas Schwab
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=20080812153015.GA8546@caradoc.them.org \
--to=drow@false.org \
--cc=apoenitz@trolltech.com \
--cc=gdb@sourceware.org \
/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