public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
Cc: Binutils <binutils@sourceware.org>
Subject: [PATCH 2/4] gprofng/testsuite: correct names for signal handling tests
Date: Fri, 16 Dec 2022 09:29:50 +0100	[thread overview]
Message-ID: <67f3d4e3-46dd-e39d-d154-49bf25dbafc8@suse.com> (raw)
In-Reply-To: <fb6f3da8-42fc-6911-fcc9-a444bc41df0c@suse.com>

The signal handling tests spend most of their time in the signal
handlers, and hence for profile output to match anything in program
output, the respective name fields need to hold the handler function
names. This converts both respective tests from "unresolved" to actually
succeeding.

--- a/gprofng/testsuite/gprofng.display/synprog/synprog.c
+++ b/gprofng/testsuite/gprofng.display/synprog/synprog.c
@@ -184,7 +184,7 @@ struct scripttab scripttab[] = {
   {"sched",     sched,          "sched",        0,  1},
   {"so",        callso,         "callso",       0,  0},
   {"sx",        callsx,         "callsx",       0,  0},
-  {"sig",       sigtime,        "sigtime",      0,  1},
+  {"sig",       sigtime,        "sigtime_handler", 0,  1},
   {"sigprof",   sigprof,        "sigprof",      1,  0},
   {"sigprof0",  sigprof,        "sigprof",      0,  0},
   {"sigprofh",  sigprofh,       "sigprofh",     1,  0},
@@ -197,7 +197,7 @@ struct scripttab scripttab[] = {
   {"uf",        underflow,      "underflow",    0,  1},
   {"forkexec",  do_forkexec,    "forkexec",     0,  0},
   {"vforkexec", do_vforkexec,   "vforkexec",    0,  0},
-  {"uwdc",      unwindcases,    "unwindcases",  0,  0},
+  {"uwdc",      unwindcases,    "unwindcases_handler", 0,  0},
   {NULL, NULL, NULL, 0, 0}
 };
 


  parent reply	other threads:[~2022-12-16  8:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16  8:26 [PATCH 0/4] gprofng: small testsuite adjustments Jan Beulich
2022-12-16  8:28 ` [PATCH 1/4] gprofng/testsuite: adjust linking of synprog Jan Beulich
2022-12-16  8:29 ` Jan Beulich [this message]
2022-12-16  8:30 ` [PATCH 3/4] gprofng/testsuite: correct line continuation in endcases.c Jan Beulich
2022-12-16  8:30 ` [PATCH 4/4] gprofng/testsuite: eliminate bogus casts Jan Beulich
2022-12-16  8:36 ` [PATCH 0/4] gprofng: small testsuite adjustments Jan Beulich
2022-12-16  9:13 ` [PATCH 5/4] gprofng/testsuite: skip Java test without JDK Jan Beulich
2022-12-16 20:16 ` [PATCH 0/4] gprofng: small testsuite adjustments Vladimir Mezentsev

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=67f3d4e3-46dd-e39d-d154-49bf25dbafc8@suse.com \
    --to=jbeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=vladimir.mezentsev@oracle.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).