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] New: "set history size unlimited" not working Date: Mon, 21 Apr 2014 22:54:00 -0000 [thread overview] Message-ID: <bug-16863-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=16863 Bug ID: 16863 Summary: "set history size unlimited" not working Product: gdb Version: 7.5 Status: NEW Severity: normal Priority: P2 Component: cli Assignee: unassigned at sourceware dot org Reporter: Bjoern at Kautler dot net https://sourceware.org/gdb/current/onlinedocs/gdb/Command-History.html#Command-History mentions that you can increase the history size to being unbound by invoking "set history size unlimited". This command is not working though. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-04-21 22:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-21 22:54 Bjoern at Kautler dot net [this message] 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 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@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: linkBe 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).