public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/14971] Failures in gdb.base/longjmp.exp Date: Thu, 17 Jan 2013 17:59:00 -0000 [thread overview] Message-ID: <bug-14971-4717-1OhVRLwhyq@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14971-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14971 --- Comment #7 from Tom Tromey <tromey at redhat dot com> 2013-01-17 17:59:00 UTC --- I think most glibc ports mangle, but what is unusual about x86 is that LD_POINTER_GUARD=0 doesn't work: http://sourceware.org/bugzilla/show_bug.cgi?id=9832 I tend to think it isn't too bad to live with a spurious FAIL or two. This is pretty much the normal state for the gdb test suite anyway. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2013-01-17 17:59 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-17 22:30 [Bug gdb/14971] New: " dblaikie at gmail dot com 2013-01-03 11:26 ` [Bug gdb/14971] " palves at redhat dot com 2013-01-03 19:37 ` dblaikie at gmail dot com 2013-01-16 18:45 ` palves at redhat dot com 2013-01-17 4:48 ` tromey at redhat dot com 2013-01-17 17:27 ` tromey at redhat dot com 2013-01-17 17:45 ` palves at redhat dot com 2013-01-17 17:59 ` tromey at redhat dot com [this message] 2013-01-17 18:08 ` palves at redhat dot com 2013-01-17 19:05 ` dblaikie at gmail dot com 2013-01-17 19:17 ` tromey at redhat dot com 2013-11-05 12:26 ` macro@linux-mips.org 2013-11-05 19:42 ` palves at redhat dot com 2013-11-12 14:59 ` tromey at redhat dot com
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-14971-4717-1OhVRLwhyq@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).