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 gdb/17756] gdb find command returns bogus results and can't find the matched value.
Date: Wed, 07 Oct 2020 18:13:56 +0000 [thread overview]
Message-ID: <bug-17756-4717-75IlLGBi8o@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17756-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17756
--- Comment #8 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=485c47e523571c1053ec4cf04d4a6b2adb7b350f
commit 485c47e523571c1053ec4cf04d4a6b2adb7b350f
Author: Tom Tromey <tromey@adacore.com>
Date: Wed Oct 7 12:07:55 2020 -0600
Add simple_search_memory unit tests
This adds some unit tests for simple_search_memory. I tried here to
reproduce some bugs (PR gdb/11158 and PR gdb/17756), but was unable
to.
gdb/ChangeLog
2020-10-07 Tom Tromey <tromey@adacore.com>
* unittests/search-memory-selftests.c: New file.
* Makefile.in (SELFTESTS_SRCS): Add
unittests/search-memory-selftests.c.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-10-07 18:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-25 9:20 [Bug gdb/17756] New: " liuyefenglin at gmail dot com
2014-12-25 9:32 ` [Bug gdb/17756] " liuyefenglin at gmail dot com
2014-12-27 8:44 ` dje at google dot com
2015-08-07 17:35 ` matt.street at gmail dot com
2015-08-07 17:57 ` palves at redhat dot com
2020-07-23 17:33 ` tromey at sourceware dot org
2020-07-23 19:00 ` tromey at sourceware dot org
2020-07-23 19:07 ` tromey at sourceware dot org
2020-07-23 19:35 ` tromey at sourceware dot org
2020-10-07 18:13 ` cvs-commit at gcc dot gnu.org [this message]
2020-10-07 18:23 ` 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-17756-4717-75IlLGBi8o@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).