public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "Bjoern at Kautler dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/16863] "set history size unlimited" not working
Date: Tue, 22 Apr 2014 01:26:00 -0000 [thread overview]
Message-ID: <bug-16863-4717-vuHgRtnekj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16863-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16863
--- Comment #3 from Björn Kautler <Bjoern at Kautler dot net> ---
Ah, ok, then it seems to be fixed in the HEAD.
In my 7.5 version it says "No symbol table loaded. Use the >>file<<-command",
or if started with an executable, "No symbol 'unlimited' in current context.".
So it seems GDB tries to resolve "unlimited" as symbol in the debugee here.
I probably should have posted this along with the report.
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-15594-listarch-gdb-prs=sources.redhat.com@sourceware.org Tue Apr 22 01:39:48 2014
Return-Path: <gdb-prs-return-15594-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 24006 invoked by alias); 22 Apr 2014 01:39:48 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 23975 invoked by uid 48); 22 Apr 2014 01:39:47 -0000
From: "sergiodj at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/16862] C-s is not working
Date: Tue, 22 Apr 2014 01:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: cli
X-Bugzilla-Version: 7.5
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sergiodj at redhat dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-16862-4717-nUsm05TpMe@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-16862-4717@http.sourceware.org/bugzilla/>
References: <bug-16862-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-q2/txt/msg00100.txt.bz2
Content-length: 1141
https://sourceware.org/bugzilla/show_bug.cgi?id\x16862
Sergio Durigan Junior <sergiodj at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |sergiodj at redhat dot com
Resolution|--- |WORKSFORME
--- Comment #1 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
C-s is shadowed by the terminal's flow control. Use "stty" to change this
behavior if you want. You can use "stty -a" to see all keybindings that are
reserved by the terminal.
In order to "fix" this bug, you can either:
(a) Disable the flow control, by using "stty -ixon"
(b) Rebind the STOP flow control, by using "stty stop ^K", where "^K" means C-k
(you can use whatever key you want).
After that, you will be able to use forward-search-history as usual. As a side
note, this affects readline programs (like bash), and not GDB alone.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-04-22 1:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 22:54 [Bug cli/16863] New: " Bjoern at Kautler dot net
2014-04-22 0:41 ` [Bug cli/16863] " sergiodj at redhat dot com
2014-04-22 0:42 ` sergiodj at redhat dot com
2014-04-22 1:26 ` Bjoern at Kautler dot net [this message]
2014-04-22 1:42 ` sergiodj at redhat dot com
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=bug-16863-4717-vuHgRtnekj@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).