From: Jonah Petri <jpetri@izotope.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: gdb@sourceware.org
Subject: Re: Completion on symbols nonfunctional, gdb 7.8.1
Date: Mon, 29 Feb 2016 17:13:00 -0000 [thread overview]
Message-ID: <CAJOrw7yKF4Z7T7fDVQ1irf55bN9iEaLu4T1KKSH3yZCDRw-O5g@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1602291646060.28664@eddie.linux-mips.org>
On Mon, Feb 29, 2016 at 11:54 AM, Maciej W. Rozycki
<macro@linux-mips.org> wrote:
> On Mon, 29 Feb 2016, Jonah Petri wrote:
>
>> Does anyone know why some gdbs (in this case 7.8.1, as built into a
>> yocto sdk) might not have working tab completion?
>
> Does "some" mean different versions installed on the same system or
> across different computers? If the latter, then have you checked for
> anything odd in /etc/inputrc or ~/.inputrc first? Distributions tend to
> put weird stuff there, which is bound to break someone's assumptions.
>
Sorry for not being specific. What I mean is that we consistently see
this behavior across all of our systems, which are all running
identical software, including gdb 7.8.1. This probably isn't
surprising :)
I should also mention that we're running gdb as root. Not sure if that matters.
I'm not familiar with inputrc, unfortunately. Can you tell me if
there's anything weird in there? I have nothing in ~root/.inputrc,
but here's the contents of /etc/inputrc:
# /etc/inputrc - global inputrc for libreadline
# See readline(3readline) and `info rluserman' for more information.
# Be 8 bit clean.
set input-meta on
set output-meta on
# To allow the use of 8bit-characters like the german umlauts, comment out
# the line below. However this makes the meta key not work as a meta key,
# which is annoying to those which don't need to type in 8-bit characters.
# set convert-meta off
# try to enable the application keypad when it is called. Some systems
# need this to enable the arrow keys.
# set enable-keypad on
# see /usr/share/doc/bash/inputrc.arrows for other codes of arrow keys
# do not bell on tab-completion
# set bell-style none
# some defaults / modifications for the emacs mode
$if mode=emacs
# allow the use of the Home/End keys
# "\e[1~": beginning-of-line
# "\e[4~": end-of-line
# allow the use of the Delete/Insert keys
# "\e[3~": delete-char
# "\e[2~": quoted-insert
# mappings for "page up" and "page down" to step to the beginning/end
# of the history
# "\e[5~": beginning-of-history
# "\e[6~": end-of-history
# alternate mappings for "page up" and "page down" to search the history
# "\e[5~": history-search-backward
# "\e[6~": history-search-forward
# # mappings for Ctrl-left-arrow and Ctrl-right-arrow for word moving
# "\e[5C": forward-word
# "\e[5D": backward-word
# "\e\e[C": forward-word
# "\e\e[D": backward-word
# $if term=rxvt
# "\e[8~": end-of-line
# $endif
# for non RH/Debian xterm, can't hurt for RH/DEbian xterm
# "\eOH": beginning-of-line
# "\eOF": end-of-line
# for freebsd console
# "\e[H": beginning-of-line
# "\e[F": end-of-line
$endif
next prev parent reply other threads:[~2016-02-29 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 16:00 Jonah Petri
2016-02-29 16:54 ` Maciej W. Rozycki
2016-02-29 17:13 ` Jonah Petri [this message]
2016-02-29 17:44 ` Maciej W. Rozycki
2016-02-29 20:49 ` Jonah Petri
2016-03-01 0:34 ` Maciej W. Rozycki
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=CAJOrw7yKF4Z7T7fDVQ1irf55bN9iEaLu4T1KKSH3yZCDRw-O5g@mail.gmail.com \
--to=jpetri@izotope.com \
--cc=gdb@sourceware.org \
--cc=macro@linux-mips.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