From: Daniel Jacobowitz <drow@false.org>
To: Peng Yu <pengyu.ut@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: How to recall the commands run in previous gdb session?
Date: Sun, 29 Oct 2006 20:49:00 -0000 [thread overview]
Message-ID: <20061029204933.GA11060@nevyn.them.org> (raw)
In-Reply-To: <366c6f340610291235u2d8a430el92c6c5353134c37e@mail.gmail.com>
On Sun, Oct 29, 2006 at 02:35:38PM -0600, Peng Yu wrote:
> Hi,
>
> In the same gdb session, I can use up or down arrow to recall commands.
>
> But once a gdb session is start over, all the history commands are
> gone. I'm wondering if it is possible to recall those commands?
Take a look at the section on saving history in the GDB manual.
Someone else asked me about this last week. I've been thinking about
adjusting it to use ~/.gdb_history instead of ./.gdb_history by default
and then enabling it by default. After all, everyone seems to assume
their shell will save CLI history, why shouldn't we?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-29 20:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 20:35 Peng Yu
2006-10-29 20:49 ` Daniel Jacobowitz [this message]
2006-10-30 4:08 ` Eli Zaretskii
2006-10-30 4:11 ` Daniel Jacobowitz
2006-10-30 21:11 ` Eli Zaretskii
2006-10-30 21:13 ` Daniel Jacobowitz
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=20061029204933.GA11060@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=pengyu.ut@gmail.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