From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [pushed 0/2] PR gdb/18002: bp-permanent.exp failures
Date: Thu, 05 Mar 2015 23:42:00 -0000 [thread overview]
Message-ID: <1425598969-7666-1-git-send-email-palves@redhat.com> (raw)
I was a bit paranoid this morning with breakage the moribund locations
rework series might have caused, and looking over buildbot results I
got confused and thought I had caused bp-permanent.exp FAILs
PPC64/gdbserver is showing... Only after fixing them did I realize
that I had compared the wrong gdb.sum files, and these failures are
pre-existing. Oh well, here's the fix. :-)
Pedro Alves (2):
PR gdb/18002: Fix reinsert of a permanent breakpoints
gdb.base/bp-permanent.exp: Tighten regex
gdb/ChangeLog | 6 ++++++
gdb/testsuite/ChangeLog | 4 ++++
gdb/mem-break.c | 11 ++++++++++-
gdb/testsuite/gdb.base/bp-permanent.exp | 2 +-
4 files changed, 21 insertions(+), 2 deletions(-)
--
1.9.3
next reply other threads:[~2015-03-05 23:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 23:42 Pedro Alves [this message]
2015-03-05 23:42 ` [pushed 1/2] PR gdb/18002: Fix reinsert of a permanent breakpoints Pedro Alves
2015-03-06 14:31 ` Yao Qi
2015-03-06 16:43 ` Pedro Alves
2015-03-05 23:42 ` [pushed 2/2] gdb.base/bp-permanent.exp: Tighten regex Pedro Alves
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=1425598969-7666-1-git-send-email-palves@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@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