public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug symtab/17602] iterate_name_matcher passes arguments to strcmp_iw in reverse order? Date: Fri, 05 Dec 2014 09:06:00 -0000 [thread overview] Message-ID: <bug-17602-4717-CDSt6sYyf3@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17602-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17602 --- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gdb and binutils". The branch, master has been updated via 642a8d806780150b62e3a0381a8d995212bdf442 (commit) from ddb9f679fa9f54633442c46574b8e5b0ca45a786 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=642a8d806780150b62e3a0381a8d995212bdf442 commit 642a8d806780150b62e3a0381a8d995212bdf442 Author: Doug Evans <xdje42@gmail.com> Date: Fri Dec 5 00:53:56 2014 -0800 Revert: linespec.c (iterate_name_matcher): Fix arguments to symbol_name_cmp. This patch causes regressions in ada's operator_bp.exp test. That's because it uses wild_match which expects arguments in the original order. There is still a bug here. It's hard to see because either minsyms save the day, or the needed symtab gets expanded before linespecs need it because of the call to cp_canonicalize_string_no_typedefs in linespec.c:find_linespec_symbols. But if you disable both of those things, then the bug is visible. bash$ ./gdb -D ./data-directory testsuite/gdb.cp/anon-ns (gdb) b doit(void) Function "doit(void)" not defined. gdb/ChangeLog: Revert: PR symtab/17602 * linespec.c (iterate_name_matcher): Fix arguments to symbol_name_cmp. ----------------------------------------------------------------------- Summary of changes: gdb/ChangeLog | 6 ++++++ gdb/linespec.c | 7 +------ 2 files changed, 7 insertions(+), 6 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-12-05 9:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-14 19:31 [Bug symtab/17602] New: " dje at google dot com 2014-11-15 0:26 ` [Bug symtab/17602] " dje at google dot com 2014-12-03 0:42 ` cvs-commit at gcc dot gnu.org 2014-12-05 9:06 ` cvs-commit at gcc dot gnu.org [this message] 2014-12-05 17:03 ` xdje42 at gmail dot com 2014-12-05 17:06 ` xdje42 at gmail dot com 2014-12-25 0:46 ` cvs-commit at gcc dot gnu.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-17602-4717-CDSt6sYyf3@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).