diff options
| author | Tom Tromey <tromey@adacore.com> | 2022-04-08 10:11:58 -0600 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2022-04-12 12:59:28 -0600 |
| commit | 36baf73637c4bd7fdaa9c6318c4c8071d82ac616 (patch) | |
| tree | 898bdcc4c922e7b043af8fdcb897f810ce59bff3 /gdb/testsuite/gdb.base/parse_number.exp | |
| parent | a8b7a1391135b63de73c1bf0e0a2f8f5dc8c6ba6 (diff) | |
| download | gdb-36baf73637c4bd7fdaa9c6318c4c8071d82ac616.zip gdb-36baf73637c4bd7fdaa9c6318c4c8071d82ac616.tar.gz gdb-36baf73637c4bd7fdaa9c6318c4c8071d82ac616.tar.bz2 | |
Fix bug in Ada number lexing
On irc, Pedro pointed out that Ada couldn't properly handle
0xffffffffffffffff. This used to work, but is a regression due to
some patches I wrote in the Ada lexer. This patch fixes the bug.
Diffstat (limited to 'gdb/testsuite/gdb.base/parse_number.exp')
| -rw-r--r-- | gdb/testsuite/gdb.base/parse_number.exp | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/gdb/testsuite/gdb.base/parse_number.exp b/gdb/testsuite/gdb.base/parse_number.exp index 8849c99..dc6d358 100644 --- a/gdb/testsuite/gdb.base/parse_number.exp +++ b/gdb/testsuite/gdb.base/parse_number.exp @@ -28,7 +28,8 @@ proc test_parse_numbers {} { set val "0xffffffffffffffff" if {$lang == "ada"} { - gdb_test "p/x $val" "Integer literal out of range" + gdb_test "p/x $val" " = 0xffffffffffffffff" + gdb_test "ptype $val" " = <8-byte integer>" } elseif {$lang == "fortran"} { gdb_test "p/x $val" " = 0xffffffff" gdb_test "ptype $val" " = unsigned int" |