From: Pedro Alves <pedro@codesourcery.com>
To: pmuldoon@redhat.com
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: [patch] [python] Prompt substitution
Date: Fri, 02 Sep 2011 17:41:00 -0000 [thread overview]
Message-ID: <201109021822.02655.pedro@codesourcery.com> (raw)
In-Reply-To: <m38vqar65n.fsf@redhat.com>
On Tuesday 30 August 2011 21:33:24, Phil Muldoon wrote:
> Pedro Alves <pedro@codesourcery.com> writes:
>
> > On Wednesday 20 July 2011 12:33:24, Phil Muldoon wrote:
> >> +gdb_test_multiple "set prompt blah " "set blah in GDB" {
> >> + -re "\[\r\n\]$newprompt2 $" {
> >> + pass "set prompt blah overriden"
> >> + }
> >> +}
> >> +
> >> +gdb_test_multiple "python gdb.prompt_hook = None" "Delete hook" {
> >> + -re "\[\r\n\]$newprompt2 $" {
> >> + pass "Delete old hook"
> >> + }
> >> +}
> >
> > Hmm:
> >
> > ...
> > PASS: gdb.python/python.exp: show prompt shows guarded prompt
> > set prompt blah
> > py prompt 2 PASS: gdb.python/python.exp: set prompt blah overriden
> > python gdb.prompt_hook = None
> > py prompt 2 PASS: gdb.python/python.exp: Delete old hook
> >
> > I think this last PASS is actually a bug. We've disabled the python
> > hook, so we should get the "set prompt" prompt back ("blah")
> > instead of still seeing the python prompt. Agree?
> >
> > (My WIP no-prompt-stack patch turned that into a FAIL,
> > but it looks like it's a bug fix, not a regression.)
>
> I think in the case, display_gdb_prompt is just displaying what GDB
> knows to be the prompt. If you delete the hook, whatever was the prompt
> when the prompt was set will remain the prompt. So the hook set the
> prompt whenever in time, and when you delete the hook, it won't restore
> what the old prompt was. So if you disable the prompt, then set prompt
> foo, then you will get "foo" now until you change it again manually. In
> the case of "guarded prompt" (IE >) it won't attempt to alter that
> display at all.
I see. I assumed that the python hook worked by overriding
"set prompt", but that the result wouldn't be seen by "show prompt".
That is, set/show prompt always worked at the "this is what
I want the prompt to look like if no scripting overrides it" level.
Okay, I preserved the current behaviour. Matt's new (uncommitted)
py-prompt.exp tests were great for making sure I did. :-)
Thanks!
--
Pedro Alves
next prev parent reply other threads:[~2011-09-02 17:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 17:09 Phil Muldoon
2011-07-19 22:58 ` Tom Tromey
2011-07-20 13:05 ` Phil Muldoon
2011-07-20 14:43 ` Tom Tromey
2011-07-21 11:15 ` Phil Muldoon
2011-08-30 19:18 ` Pedro Alves
2011-08-30 20:23 ` Phil Muldoon
2011-08-30 20:18 ` Pedro Alves
2011-08-30 20:33 ` Phil Muldoon
2011-09-02 17:41 ` Pedro Alves [this message]
2011-09-03 10:15 ` Phil Muldoon
2011-07-20 17:10 ` Eli Zaretskii
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=201109021822.02655.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.com \
--cc=tromey@redhat.com \
/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