This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] [python] Prompt substitution
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb-patches at sourceware dot org, pmuldoon at redhat dot com
- Cc: Tom Tromey <tromey at redhat dot com>
- Date: Tue, 30 Aug 2011 21:18:18 +0100
- Subject: Re: [patch] [python] Prompt substitution
- References: <m3oc0r1tjk.fsf@redhat.com> <m3ipqy2dp6.fsf@fleche.redhat.com> <m362mxxk3f.fsf@redhat.com>
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.)
--
Pedro Alves