public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Rainer Orth <ro@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-9146] testsuite: plugin: Fix gcc.dg/plugin/crash-test-write-though-null-sarif.c on Solaris
Date: Fri, 23 Feb 2024 09:07:16 +0000 (GMT)	[thread overview]
Message-ID: <20240223090716.B9F03385842A@sourceware.org> (raw)

https://gcc.gnu.org/g:6837c4503735d1bbcad0fb6e30cc139f3598f027

commit r14-9146-g6837c4503735d1bbcad0fb6e30cc139f3598f027
Author: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Date:   Fri Feb 23 10:06:41 2024 +0100

    testsuite: plugin: Fix gcc.dg/plugin/crash-test-write-though-null-sarif.c on Solaris
    
    gcc.dg/plugin/crash-test-write-though-null-sarif.c FAILs on Solaris:
    
    FAIL: gcc.dg/plugin/crash-test-write-though-null-sarif.c -fplugin=./crash_test_plugin.so  scan-sarif-file "text": "Segmentation fault
    
    Comparing the sarif files between Linux and Solaris reveals
    
    -                                                            "message": {"text": "Segmentation fault"},
    +                                                            "message": {"text": "Segmentation Fault"},
    
    This patch allows for both forms.
    
    Tested on i386-pc-solaris2.11, sparc-sun-solaris2.11, and
    x86_64-pc-linux-gnu.
    
    2024-02-22  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>
    
            gcc/testsuite:
            * gcc.dg/plugin/crash-test-write-though-null-sarif.c
            (scan-sarif-file): Allow for "Segmentation Fault", too.

Diff:
---
 gcc/testsuite/gcc.dg/plugin/crash-test-write-though-null-sarif.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/plugin/crash-test-write-though-null-sarif.c b/gcc/testsuite/gcc.dg/plugin/crash-test-write-though-null-sarif.c
index 513d66c528d5..d5d824d75fc0 100644
--- a/gcc/testsuite/gcc.dg/plugin/crash-test-write-though-null-sarif.c
+++ b/gcc/testsuite/gcc.dg/plugin/crash-test-write-though-null-sarif.c
@@ -61,4 +61,4 @@ void test_inject_write_through_null (void)
                { dg-final { scan-sarif-file "\"startColumn\": 3" } }
                { dg-final { scan-sarif-file "\"endColumn\": 31" } }
          { dg-final { scan-sarif-file "\"message\": " } }
-           { dg-final { scan-sarif-file "\"text\": \"Segmentation fault" } } */
+           { dg-final { scan-sarif-file "\"text\": \"Segmentation \[Ff\]ault" } } */

                 reply	other threads:[~2024-02-23  9:07 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=20240223090716.B9F03385842A@sourceware.org \
    --to=ro@gcc.gnu.org \
    --cc=gcc-cvs@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).