From: Don Howard <dhoward@redhat.com>
To: <gdb@sources.redhat.com>
Subject: Re: Redefining built-in commands.
Date: Thu, 30 May 2002 17:37:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0205301730050.8589-100000@theotherone> (raw)
In-Reply-To: <Pine.LNX.4.33.0205301449040.8589-100000@theotherone>
On Thu, 30 May 2002, Don Howard wrote:
>
>
> I've run across a bug involving redefinition of built-in commands:
>
> If the command has an alias, the alias is not redefined. Instead, the
> alias is left in an inconsistent state and causes a crash when invoked.
>
> Should gdb allow users to redefine built-in commands? If so, should the
> orignial alias continue to behave like the original built-in, or should
> it's behavior be modified also?
>
An example:
(gdb) define next
Really redefine built-in command "next"? (y or n) y
Type commands for definition of "next".
End with a line saying just "end".
>echo A silly example - redefine next\n
>end
(gdb) next
A silly example - redefine next
(gdb) n
Segmentation fault
--
dhoward@redhat.com
gdb engineering
next prev parent reply other threads:[~2002-05-31 0:37 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 [this message]
2002-05-31 0:29 ` Eli Zaretskii
2002-06-05 14:39 ` Don Howard
2002-06-10 9:23 ` Tom Tromey
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=Pine.LNX.4.33.0205301730050.8589-100000@theotherone \
--to=dhoward@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