public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/17762] New: template lookup: partial syms vs syms differences
Date: Sat, 27 Dec 2014 07:10:00 -0000 [thread overview]
Message-ID: <bug-17762-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=17762
Bug ID: 17762
Summary: template lookup: partial syms vs syms differences
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: symtab
Assignee: unassigned at sourceware dot org
Reporter: dje at google dot com
While debugging a failure in a sandbox I noticed odd behaviour with the
templates.exp testcase.
psyms have this (from mt print psym):
Baz<int, (char)'\\001>::baz
yet syms have Baz<int, (char)1>::baz
and while single stepping through symbol lookup via quick fns, the lookup
failed,
as expected, because the "(char)1" version was passed for lookup and was
compared with the "(char)'\\001'" version in the psym table.
Is there a real problem here?
Filing this so it's not forgotten.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-12-27 7:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 7:10 dje at google dot com [this message]
2014-12-27 7:35 ` [Bug symtab/17762] " dje at google dot com
2022-10-21 17:19 ` tromey at sourceware dot org
2022-10-21 17:20 ` tromey at sourceware dot org
2022-10-21 17:37 ` tromey at sourceware dot org
2022-10-21 17:43 ` tromey at sourceware dot org
2023-01-11 23:47 ` dblaikie at gmail dot com
2023-02-25 1:55 ` tromey at sourceware dot org
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=bug-17762-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).