public inbox for binutils-cvs@sourceware.org help / color / mirror / Atom feed
From: Vladimir Mezentsev <vmezents@sourceware.org> To: bfd-cvs@sourceware.org, gdb-cvs@sourceware.org Subject: [binutils-gdb/binutils-2_39-branch] gprofng: fix bug 29410 - Argument " 0." isn't numeric in numeric gt (>) Date: Wed, 3 Aug 2022 17:34:13 +0000 (GMT) [thread overview] Message-ID: <20220803173413.E10823858C39@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7ca38082b7b66d6604495b47ca253f723a5b7e5c commit 7ca38082b7b66d6604495b47ca253f723a5b7e5c Author: Ruud van der Pas <ruud.vanderpas@oracle.com> Date: Tue Aug 2 10:13:48 2022 -0700 gprofng: fix bug 29410 - Argument " 0." isn't numeric in numeric gt (>) gprofng/Changelog: 2022-08-02 Ruud van der Pas <ruud.vanderpas@oracle.com> PR gprofng/29410 * gp-display-html/gp-display-html.in: Remove non-breaking spaces. Diff: --- gprofng/gp-display-html/gp-display-html.in | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/gprofng/gp-display-html/gp-display-html.in b/gprofng/gp-display-html/gp-display-html.in index ab21dbb0862..8131ecf4677 100644 --- a/gprofng/gp-display-html/gp-display-html.in +++ b/gprofng/gp-display-html/gp-display-html.in @@ -6020,6 +6020,12 @@ sub generate_dis_html my $current_value; my $max_value; $current_value = $current_metrics[$metric]; +#------------------------------------------------------------------------------ +# As part of the padding process, non-breaking spaces may have been inserted +# in an earlier phase. Temporarily remove these to make sure that the maximum +# metric values can be computed. +#------------------------------------------------------------------------------ + $current_value =~ s/ //g; if (exists ($max_metric_values[$metric])) { $max_value = $max_metric_values[$metric];
reply other threads:[~2022-08-03 17:34 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=20220803173413.E10823858C39@sourceware.org \ --to=vmezents@sourceware.org \ --cc=bfd-cvs@sourceware.org \ --cc=gdb-cvs@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).