public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jifl-bugzilla at jifvik dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/15962] break / rbreak fails to match C linkage C++ functions with user-defined types Date: Tue, 03 Feb 2015 22:10:00 -0000 [thread overview] Message-ID: <bug-15962-4717-MdiXP7PJbf@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15962-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=15962 --- Comment #1 from Jonathan Larmour <jifl-bugzilla at jifvik dot org> --- Created attachment 8099 --> https://sourceware.org/bugzilla/attachment.cgi?id=8099&action=edit Candidate patch to try with and without canonicalization Hi, I've come back to this issue as it is still present in 7.8.2. The suggested fix I proposed was not right - cp_canonicalize_string_no_typedefs() will eventually call lookup_symbol() (via replace_typedefs() or inspect_type()) which can cause infinite recursion. Therefore I am attaching a possible more straightforward fix which is to adjust find_linespec_symbols() so that it first tries to find a function symbol for the passed-in name, and only then repeats the search with a canonicalized version of the name. It certainly fixes the reported issue. So can someone have a look at it? Thanks. I do have an FSF assignment. Jifl 2014-02-03 Jonathan Larmour <jifl@eCosCentric.com> PR symtab/15962 * linespec.c (find_linespec_symbols): Attempt to find function symbol both without and with C++ canonicalization. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-02-03 22:09 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-16 22:04 [Bug symtab/15962] New: " jifl-bugzilla at jifvik dot org 2015-02-03 22:10 ` jifl-bugzilla at jifvik dot org [this message] 2015-02-03 22:12 ` [Bug symtab/15962] " jifl-bugzilla at jifvik dot org 2015-02-03 22:41 ` jifl-bugzilla at jifvik dot org 2024-01-11 18:06 ` ssbssa 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-15962-4717-MdiXP7PJbf@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: linkBe 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).