Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: fix PR 12707
Date: Tue, 15 Jan 2013 17:22:00 -0000	[thread overview]
Message-ID: <20130115172149.GA21127@host2.jankratochvil.net> (raw)
In-Reply-To: <87r4lno936.fsf@fleche.redhat.com>

On Mon, 14 Jan 2013 20:31:09 +0100, Tom Tromey wrote:
> Second, I had to change cmpd-minsyms.exp to account for the symtab.c
> change, which in turn was required to align symbol_find_demangled_name
> with what dwarf2read.c is doing.

Yes, this is a problem I faced when thinking about fixing this issue:


$ nm -C gdb.cp/cmpd-minsyms
000000000040067d W int GDB<char>::even_harder<int>(char)
FSF GDB:
(gdb) b int GDB<char>::even_harder<int>(char)
Breakpoint 1 at 0x400681
patched GDB:
(gdb) b int GDB<char>::even_harder<int>(char)
Function "int GDB<char>::even_harder<int>(char)" not defined.
Make breakpoint pending on future shared library load? (y or [n]) 

(The ticks ' do not help it.)

I find "int GDB<char>::even_harder<int>(char)" to be a valid (or at least also
valid) demangled name for that function so I believe GDB should know that
name.


Thanks,
Jan


  parent reply	other threads:[~2013-01-15 17:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 19:31 Tom Tromey
2013-01-15 15:12 ` Pedro Alves
2013-01-15 15:32   ` Tom Tromey
2013-01-15 16:59 ` Jan Kratochvil
2013-01-15 17:05   ` Tom Tromey
2013-01-15 17:22 ` Jan Kratochvil [this message]
2013-01-17 21:25   ` Tom Tromey
2013-01-17 21:54     ` Jan Kratochvil
2013-01-17 21:59       ` Tom Tromey
2013-01-17 22:04         ` Jan Kratochvil
2013-01-17 22:33           ` Jan Kratochvil
2013-01-18 14:31           ` Tom Tromey
2013-01-18 14:35             ` Jan Kratochvil
2013-01-18 15:04               ` Tom Tromey
2013-01-18 15:33                 ` Jan Kratochvil

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=20130115172149.GA21127@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.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