From: Doug Evans <dje@google.com>
To: Jan Engelhardt <jengelh@inai.de>
Cc: gdb@sourceware.org, Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Re: "j" is now an ambiguous command
Date: Wed, 19 Sep 2012 20:23:00 -0000 [thread overview]
Message-ID: <CADPb22R8yCyMpfH_8xpwRhw3_J2E44FopRmG+Aoffn-84S3xLQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1209160050010.13178@nerf07.vanv.qr>
Hi. Just a followup (patch checked into trunk by sergiodj).
You can work around this in the mean time by adding this to your ~/.gdbinit:
alias j = jump
On Sat, Sep 15, 2012 at 3:54 PM, Jan Engelhardt <jengelh@inai.de> wrote:
>
> Between gdb-7.3 and 7.4.50.20120603, gdb has gained the two commands
> "jit-reader-load" and "jit-reader-unload".
> This causes "j", previously used as a shortcut for "jump", to have
> become ambiguous. I would ask for "j" to be recognized again, similar to
> how "b" is synonymous with "break" despite the presence of other b*
> commands.
>
> (gdb) j 1762
> Ambiguous command "j 1762": jit-reader-load, jit-reader-unload, jump.
>
> thanks,
> Jan
prev parent reply other threads:[~2012-09-19 20:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 22:54 Jan Engelhardt
2012-09-19 20:23 ` Doug Evans [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=CADPb22R8yCyMpfH_8xpwRhw3_J2E44FopRmG+Aoffn-84S3xLQ@mail.gmail.com \
--to=dje@google.com \
--cc=gdb@sourceware.org \
--cc=jengelh@inai.de \
--cc=sergiodj@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).