From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH 3/9] Enable "set debug parser" for Ada
Date: Mon, 7 Mar 2022 09:04:46 -0700 [thread overview]
Message-ID: <20220307160452.3765943-4-tromey@adacore.com> (raw)
In-Reply-To: <20220307160452.3765943-1-tromey@adacore.com>
I noticed that "set debug parser 1" did not affect Ada parsing. This
patch fixes the problem.
Because this is rarely useful, and pretty much only for maintainers, I
didn't write a test case.
---
gdb/ada-exp.y | 3 +++
1 file changed, 3 insertions(+)
diff --git a/gdb/ada-exp.y b/gdb/ada-exp.y
index c974657dbcd..a46ec991d70 100644
--- a/gdb/ada-exp.y
+++ b/gdb/ada-exp.y
@@ -1081,6 +1081,9 @@ ada_parse (struct parser_state *par_state)
gdb_assert (par_state != NULL);
pstate = par_state;
+ scoped_restore restore_yydebug = make_scoped_restore (&yydebug,
+ parser_debug);
+
lexer_init (yyin); /* (Re-)initialize lexer. */
obstack_free (&temp_parse_space, NULL);
obstack_init (&temp_parse_space);
--
2.34.1
next prev parent reply other threads:[~2022-03-07 16:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 16:04 [PATCH 0/9] Context-sensitive completion " Tom Tromey
2022-03-07 16:04 ` [PATCH 1/9] Remove null sentinel from 'attributes' Tom Tromey
2022-03-07 16:04 ` [PATCH 2/9] Fix bug in Ada attributes lexing Tom Tromey
2022-03-07 16:04 ` Tom Tromey [this message]
2022-03-07 16:04 ` [PATCH 4/9] Refactor expression completion Tom Tromey
2022-03-07 16:04 ` [PATCH 5/9] Implement completion for Ada attributes Tom Tromey
2022-03-07 16:04 ` [PATCH 6/9] Refactor ada-lex.l:processId Tom Tromey
2022-03-07 16:04 ` [PATCH 7/9] Remove the Ada DOT_ALL token Tom Tromey
2022-03-07 16:04 ` [PATCH 8/9] Consolidate single-char tokens in ada-lex.l Tom Tromey
2022-03-07 16:04 ` [PATCH 9/9] Add context-sensitive field name completion to Ada parser Tom Tromey
2022-04-04 18:49 ` [PATCH 0/9] Context-sensitive completion for Ada Tom Tromey
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=20220307160452.3765943-4-tromey@adacore.com \
--to=tromey@adacore.com \
--cc=gdb-patches@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: 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).