From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: fix PR 12707
Date: Fri, 18 Jan 2013 14:31:00 -0000 [thread overview]
Message-ID: <874niebm24.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20130117220437.GA18386@host2.jankratochvil.net> (Jan Kratochvil's message of "Thu, 17 Jan 2013 23:04:37 +0100")
Tom> I expect it will break expression parsing.
Jan> Then it should be fixed but IIRC it works with the linespec parser even
Jan> without quotes.
I don't think we're talking about the same thing.
I was contemplating the change you implied -- adding return types to all
symbols. I think this change would make symbol lookup during expression
parsing fail. In this case one does not include the return type in the
lookup name.
It works ok now precisely because the debug symbols don't include this
information. Here it is without debuginfo:
(gdb) p GDB<char>::even_harder<int> ('a')
No symbol "GDB<char>" in current context.
(gdb) p 'int GDB<char>::even_harder<int>' ('a')
$1 = 97
Tom> I think that would require too much memory for what is really a marginal
Tom> feature.
Jan> I find it an essential feature to be able to break on function where the
Jan> application has crashed, I was using it myself several times for some C++
Jan> application (Firefox probably).
Ok. I'm going to drop this patch.
Tom
next prev parent reply other threads:[~2013-01-18 14:31 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
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 [this message]
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=874niebm24.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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