From: Steven Johnson <sjohnson@neurizon.net>
To: Fernando Nasser <fnasser@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: Post Hooks Broken!!! Fix Attached.
Date: Sun, 25 Feb 2001 21:11:00 -0000 [thread overview]
Message-ID: <3A99E57C.85A8A3C1@neurizon.net> (raw)
In-Reply-To: <3A9668CF.EF616BCE@redhat.com>
Hi Fernando,
Fernando Nasser wrote:
>
> Hi Steven,
>
> It was before that. I went through the archives and it seems that it
> was broken when the the 'if' statement that referred to PRE_HOOK was
> changed to a 'switch' on "hook_type", with the CMD_{PRE,POST}_HOOK
> enums.
>
> I will check the patch in latter today, but this shows that we need a
> test for this.
>
Doesn't surprise me, I hadn't done anything with GDB for a while.
> Can you send me a sequence of commands and expected responses that would
> test if the post hook has been correctly installed and another one
> showing that the pre hook has not been clobbered? I can use it to
> create a dejagnu test for it.
Here it is:
(gdb)echo hooked
hooked
(gdb)define hook-echo
>echo before
>end
(gdb)echo hooked
beforehooked
(gdb)define hookpost-echo
>echo after
>end
(gdb)echo hooked
beforehookedafter
(gdb)define hook-echo
>end
(gdb)echo hooked
hookedafter
(gdb)define hookpost-echo
>end
(gdb)echo hooked
hooked
(gdb)
I hope this is what you were looking for? I used echo, because I
thought it would be easy to test with it on every platform. Obviously
there are a few permutations of this but Im not sure they are worth
checking individually.
Regards,
Steven Johnson
prev parent reply other threads:[~2001-02-25 21:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 22:02 Steven Johnson
2001-02-23 5:45 ` Fernando Nasser
2001-02-25 21:11 ` Steven Johnson [this message]
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=3A99E57C.85A8A3C1@neurizon.net \
--to=sjohnson@neurizon.net \
--cc=fnasser@redhat.com \
--cc=gdb@sources.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