From: Phil Muldoon <pmuldoon@redhat.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [patch] Fix Python rbreak tests setting too many breakpoints
Date: Wed, 29 Nov 2017 16:32:00 -0000 [thread overview]
Message-ID: <5ce5db13-f5c7-a4f2-9e5e-0e669580f2eb@redhat.com> (raw)
Pedro noticed that when glibc debug info is installed the Python
rbreak fails by setting far too many breakpoints. This patch excludes
these symbols by setting "nosharedlibrary" before the tests run.
Cheers
Phil
--
2017-11-29 Phil Muldoon <pmuldoon@redhat.com>
* gdb.python/py-rbreak.exp: Set nosharedlibrary before tests.
* gdb.cp/psymtab-parameter.cc (func): Change return type back to long.
diff --git a/gdb/testsuite/gdb.python/py-rbreak.exp b/gdb/testsuite/gdb.python/py-rbreak.exp
index 5aaf2975c9..3cf158bb02 100644
--- a/gdb/testsuite/gdb.python/py-rbreak.exp
+++ b/gdb/testsuite/gdb.python/py-rbreak.exp
@@ -32,6 +32,7 @@ if ![runto_main] then {
return 0
}
+gdb_test_no_output "nosharedlibrary"
gdb_py_test_silent_cmd "py sl = gdb.rbreak(\"\",minsyms=False)" \
"get all function breakpoints" 0
gdb_test "py print(len(sl))" "11" \
next reply other threads:[~2017-11-29 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 16:32 Phil Muldoon [this message]
2017-11-29 16:35 ` 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=5ce5db13-f5c7-a4f2-9e5e-0e669580f2eb@redhat.com \
--to=pmuldoon@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