public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom de Vries <vries@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] [gdb/m2] Fix UB and literal truncation Date: Sat, 4 Jun 2022 11:18:09 +0000 (GMT) [thread overview] Message-ID: <20220604111809.180893839C7B@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=999f7adc21cdcef5b606d2529068121dc6032b18 commit 999f7adc21cdcef5b606d2529068121dc6032b18 Author: Tom de Vries <tdevries@suse.de> Date: Sat Jun 4 13:17:33 2022 +0200 [gdb/m2] Fix UB and literal truncation Rewrite parse_number to use ULONGEST instead of LONGEST, to fix UB errors as mentioned in PR29163. Furthermore, make sure we error out on overflow instead of truncating in all cases. Tested on x86_64-linux, with a build with --enable-targets=all. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29163 Diff: --- gdb/m2-exp.y | 47 ++++++++++++++++----------------- gdb/testsuite/gdb.base/parse_number.exp | 3 +-- 2 files changed, 24 insertions(+), 26 deletions(-) diff --git a/gdb/m2-exp.y b/gdb/m2-exp.y index 85bac11b8fb..d3e917bb8d7 100644 --- a/gdb/m2-exp.y +++ b/gdb/m2-exp.y @@ -582,12 +582,11 @@ static int parse_number (int olen) { const char *p = pstate->lexptr; - LONGEST n = 0; - LONGEST prevn = 0; + ULONGEST n = 0; + ULONGEST prevn = 0; int c,i,ischar=0; int base = input_radix; int len = olen; - int unsigned_p = number_sign == 1 ? 1 : 0; if(p[len-1] == 'H') { @@ -639,16 +638,11 @@ parse_number (int olen) n+=i; if(i >= base) return ERROR; - if(!unsigned_p && number_sign == 1 && (prevn >= n)) - unsigned_p=1; /* Try something unsigned */ - /* Don't do the range check if n==i and i==0, since that special - case will give an overflow error. */ - if(RANGE_CHECK && n!=i && i) - { - if((unsigned_p && (unsigned)prevn >= (unsigned)n) || - ((!unsigned_p && number_sign==-1) && -prevn <= -n)) - range_error (_("Overflow on numeric constant.")); - } + if (n == 0 && prevn == 0) + ; + else if (RANGE_CHECK && prevn >= n) + range_error (_("Overflow on numeric constant.")); + prevn=n; } @@ -661,17 +655,22 @@ parse_number (int olen) yylval.ulval = n; return CHAR; } - else if ( unsigned_p && number_sign == 1) - { - yylval.ulval = n; - return UINT; - } - else if((unsigned_p && (n<0))) { - range_error (_("Overflow on numeric constant -- number too large.")); - /* But, this can return if range_check == range_warn. */ - } - yylval.lval = n; - return INT; + + int int_bits = gdbarch_int_bit (pstate->gdbarch ()); + bool have_signed = number_sign == -1; + bool have_unsigned = number_sign == 1; + if (have_signed && fits_in_type (number_sign, n, int_bits, true)) + { + yylval.lval = n; + return INT; + } + else if (have_unsigned && fits_in_type (number_sign, n, int_bits, false)) + { + yylval.ulval = n; + return UINT; + } + else + error (_("Overflow on numeric constant.")); } diff --git a/gdb/testsuite/gdb.base/parse_number.exp b/gdb/testsuite/gdb.base/parse_number.exp index 4189ccaf92c..6e0091278a9 100644 --- a/gdb/testsuite/gdb.base/parse_number.exp +++ b/gdb/testsuite/gdb.base/parse_number.exp @@ -161,8 +161,7 @@ proc parse_number { lang n } { return [list "CARDINAL" $n] } else { # Overflow. - # Some truncated value or re_overflow, should be re_overflow. - return [list ($re_overflow|CARDINAL|INTEGER) ($re_overflow|$any)] + return [list $re_overflow $re_overflow] } } elseif { $lang == "fortran" } { if { [fits_in_type $n $int_bits s] } {
reply other threads:[~2022-06-04 11:18 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=20220604111809.180893839C7B@sourceware.org \ --to=vries@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).