public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: David Malcolm <dmalcolm@redhat.com>
Subject: [pushed 2/2] jit.exp: handle dwarf version mismatch in jit-check-debug-info [PR110466]
Date: Fri, 30 Jun 2023 11:54:09 -0400	[thread overview]
Message-ID: <20230630155409.183039-2-dmalcolm@redhat.com> (raw)
In-Reply-To: <20230630155409.183039-1-dmalcolm@redhat.com>

Successfully regrtested on x86_64-pc-linux-gnu.
Verified fix on powerpc64le-unknown-linux-gnu (gcc112 in Compile Farm).
Pushed to trunk as r14-2223-gc3c0ba5436170e.

gcc/testsuite/ChangeLog:
	PR jit/110466
	* jit.dg/jit.exp (jit-check-debug-info): Gracefully handle too
	early versions of gdb that don't support our dwarf version, via
	"unsupported".
---
 gcc/testsuite/jit.dg/jit.exp | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/gcc/testsuite/jit.dg/jit.exp b/gcc/testsuite/jit.dg/jit.exp
index 3568dbb9d63..8bf7e51c24f 100644
--- a/gcc/testsuite/jit.dg/jit.exp
+++ b/gcc/testsuite/jit.dg/jit.exp
@@ -440,6 +440,10 @@ proc jit-check-debug-info { obj_file cmds match } {
         send $cmd
     }
     expect {
+	-re "Dwarf Error: wrong version in compilation unit header" {
+	    set testcase [testname-for-summary]
+	    unsupported "$testcase: gdb does not support dwarf version"
+	}
         -re $match { pass OK }
         default { fail FAIL }
     }
-- 
2.26.3


      reply	other threads:[~2023-06-30 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 15:54 [pushed 1/2] jit: avoid using __vector in testcase [PR110466] David Malcolm
2023-06-30 15:54 ` David Malcolm [this message]

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=20230630155409.183039-2-dmalcolm@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).