From: Jan Engelhardt <jengelh@inai.de>
To: gdb@sourceware.org
Subject: "j" is now an ambiguous command
Date: Sat, 15 Sep 2012 22:54:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.01.1209160050010.13178@nerf07.vanv.qr> (raw)
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
next reply other threads:[~2012-09-15 22:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 22:54 Jan Engelhardt [this message]
2012-09-19 20:23 ` Doug Evans
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=alpine.LNX.2.01.1209160050010.13178@nerf07.vanv.qr \
--to=jengelh@inai.de \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).