From: Simon Marchi <simon.marchi@efficios.com>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: [PATCH 09/13] gdb: remove backslash-newline handling from cp_parse_escape
Date: Tue, 20 Oct 2026 12:17:31 -0400 [thread overview]
Message-ID: <20261020162054.2140671-10-simon.marchi@efficios.com> (raw)
In-Reply-To: <20261020162054.2140671-1-simon.marchi@efficios.com>
From: Simon Marchi <simon.marchi@polymtl.ca>
cp_parse_escape returns -2 when the backslash is followed by a newline.
In source code, a backslash-newline is a line splice, which can appear
anywhere, including in string literals. But cp_parse_escape does not
need to handle that.
This comes from GDB's old generic parse_escape function, where a negative
value told the caller to treat the sequence as nothing at all, emulating a
line splice. lex_char_literal doesn't even handle that: it uses the
returned -2 as the value of the character, so C<'\<newline>'> canonicalizes
to "C<(char)-2>".
Remove the special case. A backslash followed by a newline is now
handled like any other unknown escape sequence, giving the character
following the backslash. So now, C<'\<newline>'> canonicalizes to
"C<(char)10>". cp_parse_escape doesn't reject unknown escape sequences
in general, which is acceptable, and we don't expect to see this one in
practice anyway.
Update the comment of cp_parse_escape, which mentioned the negative
value for backslash-newline.
Change-Id: I25a4587309f201ac8da2ae87361ad4f3e89d7327
---
gdb/cp-name-parser.c | 5 -----
1 file changed, 5 deletions(-)
diff --git a/gdb/cp-name-parser.c b/gdb/cp-name-parser.c
index 4c5f18c9851f..931f74e8ed51 100644
--- a/gdb/cp-name-parser.c
+++ b/gdb/cp-name-parser.c
@@ -470,9 +470,6 @@ c_parse_backslash (int host_char, int *target_char)
is updated past the characters we use. The value of the
escape sequence is returned.
- A negative value means the sequence \ newline was seen,
- which is supposed to be equivalent to nothing at all.
-
If \ is followed by a null character, we return a negative
value and leave the string pointer pointing at the null character.
@@ -489,8 +486,6 @@ cp_parse_escape (const char **string_ptr)
else
switch (c)
{
- case '\n':
- return -2;
case 0:
(*string_ptr)--;
return 0;
--
2.56.0
next prev parent reply other threads:[~2026-10-20 16:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 16:17 [PATCH 00/13] Make the C++ name parser recognize more char literal forms Simon Marchi
2026-10-20 16:17 ` [PATCH 01/13] gdb: make demangle_parse_info own the memory its tree points into Simon Marchi
2026-10-20 16:17 ` [PATCH 02/13] gdb: remove p_allocated_size parameter of gdb_cplus_demangle_print Simon Marchi
2026-10-20 16:17 ` [PATCH 03/13] gdb: modernize mangled_name_to_comp and cp_class_name_from_physname Simon Marchi
2026-10-20 16:17 ` [PATCH 04/13] gdb: fix crash in "maint canonicalize" without argument Simon Marchi
2026-10-20 16:17 ` [PATCH 05/13] gdb: move C++ name parser parsing selftest to its own test Simon Marchi
2026-10-20 16:17 ` [PATCH 06/13] gdb: check exact results in the canonicalize selftest Simon Marchi
2026-10-21 15:21 ` Tom Tromey
2026-10-21 15:48 ` Simon Marchi
2026-10-21 16:56 ` Tom Tromey
2026-10-21 17:01 ` Simon Marchi
2026-10-21 17:48 ` Tom Tromey
2026-10-22 16:28 ` Simon Marchi
2026-10-20 16:17 ` [PATCH 07/13] gdb: extract lex_char_literal from cpname_yylex Simon Marchi
2026-10-21 15:22 ` Tom Tromey
2026-10-20 16:17 ` [PATCH 08/13] gdb: remove \^ escape sequence support from C++ name parser Simon Marchi
2026-10-20 16:17 ` Simon Marchi [this message]
2026-10-20 16:17 ` [PATCH 10/13] gdb: fix out-of-bounds reads in lex_char_literal Simon Marchi
2026-10-20 16:17 ` [PATCH 11/13] gdb: handle hexadecimal escapes in C++ name parser Simon Marchi
2026-10-20 16:17 ` [PATCH 12/13] gdb: handle character literal encoding prefixes " Simon Marchi
2026-10-20 16:17 ` [PATCH 13/13] gdb: handle universal character names " Simon Marchi
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=20261020162054.2140671-10-simon.marchi@efficios.com \
--to=simon.marchi@efficios.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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