Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [rfa/x86-64] Supress x86-64 structs.exp test?
Date: Thu, 20 Nov 2003 18:23:00 -0000	[thread overview]
Message-ID: <3FBD069F.9000504@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 273 bytes --]

I just ran the new structs.exp on amd64.  Turns out amd digs a hole so 
deep that GDB gets stuck in free fall (an infinite loop resuming the 
target?).  The attached supresses the testfile until someone gets the 
chance to see whats really happening.

thoughts? ok?
Andrew

[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 706 bytes --]

2003-11-20  Andrew Cagney  <cagney@redhat.com>

	* gdb.base/structs.exp: Suppress when "x86_64-*-*".

Index: gdb.base/structs.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/structs.exp,v
retrieving revision 1.9
diff -u -r1.9 structs.exp
--- gdb.base/structs.exp	20 Nov 2003 18:03:48 -0000	1.9
+++ gdb.base/structs.exp	20 Nov 2003 18:15:50 -0000
@@ -35,6 +35,13 @@
     continue
 }
 
+# struct return on x86-64 is very broken
+switch -glob -- [istarget] {
+    "x86_64-*-*" {
+	gdb_suppress_entire_file "amd64 is really broken"
+    }
+}
+
 set testfile "structs"
 set srcfile ${testfile}.c
 set binfile ${objdir}/${subdir}/${testfile}

             reply	other threads:[~2003-11-20 18:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20 18:23 Andrew Cagney [this message]
2003-11-20 22:46 ` Mark Kettenis
2003-11-27 20:44   ` Mark Kettenis
2003-12-01 14:55     ` Andrew Cagney

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=3FBD069F.9000504@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    /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