From: Tom Tromey <tromey@redhat.com>
To: Don Howard <dhoward@redhat.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, <gdb@sources.redhat.com>
Subject: Re: Redefining built-in commands.
Date: Mon, 10 Jun 2002 09:23:00 -0000 [thread overview]
Message-ID: <87bsajt7jk.fsf@creche.redhat.com> (raw)
In-Reply-To: Don Howard's message of "Wed, 5 Jun 2002 14:39:44 -0700 (PDT)"
>>>>> "Don" == Don Howard <dhoward@redhat.com> writes:
Don> (gdb) define step
Don> do something special
Don> step
Don> end
Don> (gdb)
Don> The above example ends up "doing something special" until gdb hits it's
Don> recursion limit, rather than doing something special and then stepping.
Don> The example *does* work just fine if the user picks anything other than a
Don> built-in name:
Bash solves this problem by adding a `command' command, which invokes
the original command. So in the above you could use `command step' to
invoke the real step. Perhaps this would be useful in gdb.
Tom
prev parent reply other threads:[~2002-06-10 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 17:23 Don Howard
2002-05-30 17:37 ` Don Howard
2002-05-31 0:29 ` Eli Zaretskii
2002-06-05 14:39 ` Don Howard
2002-06-10 9:23 ` Tom Tromey [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=87bsajt7jk.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=dhoward@redhat.com \
--cc=eliz@is.elta.co.il \
--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