public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom de Vries <vries@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] [gdb/testsuite] Detect 'No MPX support' Date: Thu, 14 Apr 2022 10:32:54 +0000 (GMT) [thread overview] Message-ID: <20220414103254.A81D63857418@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=75b2a443d515f531299ce1ed942810edd5bf5d84 commit 75b2a443d515f531299ce1ed942810edd5bf5d84 Author: Tom de Vries <tdevries@suse.de> Date: Thu Apr 14 12:32:51 2022 +0200 [gdb/testsuite] Detect 'No MPX support' On openSUSE Leap 15.3, mpx support has been disabled for m32, so I run into: ... (gdb) run ^M Starting program: outputs/gdb.arch/i386-mpx/i386-mpx ^M [Thread debugging using libthread_db enabled]^M Using host libthread_db library "/lib64/libthread_db.so.1".^M No MPX support^M ... and eventually into all sort of fails in this and other mpx test-cases. Fix this by detecting the "No MPX support" message in have_mpx. Tested on x86_64-linux with target boards unix and unix/-m32. Diff: --- gdb/testsuite/lib/gdb.exp | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp index 902fb4a7b5e..7c35fbb18c4 100644 --- a/gdb/testsuite/lib/gdb.exp +++ b/gdb/testsuite/lib/gdb.exp @@ -8329,6 +8329,29 @@ gdb_caching_proc have_mpx { remote_file build delete $obj + if { $status == 0 } { + verbose "$me: returning $status" 2 + return $status + } + + # Compile program with -mmpx -fcheck-pointer-bounds, try to trigger + # 'No MPX support', in other words, see if kernel supports mpx. + set src { int main (void) { return 0; } } + set comp_flags {} + append comp_flags " additional_flags=-mmpx" + append comp_flags " additional_flags=-fcheck-pointer-bounds" + if {![gdb_simple_compile $me-2 $src executable $comp_flags]} { + return 0 + } + + set result [remote_exec target $obj] + set status [lindex $result 0] + set output [lindex $result 1] + set status [expr ($status == 0) \ + && ![string equal $output "No MPX support\r\n"]] + + remote_file build delete $obj + verbose "$me: returning $status" 2 return $status }
reply other threads:[~2022-04-14 10:32 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220414103254.A81D63857418@sourceware.org \ --to=vries@sourceware.org \ --cc=gdb-cvs@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).