From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Doug Evans <dje@google.com>
Subject: Re: [PATCH] fix thinko in pre/post hook help output
Date: Sat, 30 Aug 2008 00:18:00 -0000 [thread overview]
Message-ID: <200808300118.26587.pedro@codesourcery.com> (raw)
In-Reply-To: <20080829235547.5279D1C7801@localhost>
On Saturday 30 August 2008 00:55:47, Doug Evans wrote:
> fyi, checked in as obvious (swap before/after).
>
> 2008-08-29 Doug Evans <dje@google.com>
>
> * cli/cli-decode.c (help_cmd): Fix thinko in pre/post hook help output.
>
> Index: cli/cli-decode.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/cli/cli-decode.c,v
> retrieving revision 1.69
> diff -u -p -u -p -r1.69 cli-decode.c
> --- cli/cli-decode.c 30 Jul 2008 01:10:17 -0000 1.69
> +++ cli/cli-decode.c 29 Aug 2008 23:48:28 -0000
> @@ -797,12 +797,12 @@ help_cmd (char *command, struct ui_file
> "\nThis command has a hook (or hooks) defined:\n");
>
> if (c->hook_pre)
> - fprintf_filtered (stream,
> - "\tThis command is run after : %s (pre hook)\n",
> + fprintf_filtered (stream,
> + "\tThis command is run before : %s (pre hook)\n",
> c->hook_pre->name);
I don't think this change is correct. The command refered to in this
context does run *after* the pre-hook,
> if (c->hook_post)
> - fprintf_filtered (stream,
> - "\tThis command is run before : %s (post hook)\n",
> + fprintf_filtered (stream,
> + "\tThis command is run after : %s (post hook)\n",
> c->hook_post->name);
> }
and *before* the post-hook runs. E.g.,
(gdb) define hook-thread
Type commands for definition of "hook-thread".
End with a line saying just "end".
>print "before"
>end
(gdb) help thread
...
This command has a hook (or hooks) defined:
This command is run after : hook-thread (pre hook)
(gdb) thread
$1 = "before"
[Current thread is 1 (Thread 0x7ffff7fd46e0 (LWP 7467))]
(gdb)
"thread" does runs *after* "hook-thread".
--
Pedro Alves
next prev parent reply other threads:[~2008-08-30 0:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 23:56 Doug Evans
2008-08-30 0:18 ` Pedro Alves [this message]
2008-08-30 1:56 ` Doug Evans
2008-08-30 15:05 ` Pedro Alves
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=200808300118.26587.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=dje@google.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