From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: How to recall the commands run in previous gdb session?
Date: Mon, 30 Oct 2006 21:13:00 -0000 [thread overview]
Message-ID: <20061030211347.GA22489@nevyn.them.org> (raw)
In-Reply-To: <ur6wp7c5h.fsf@gnu.org>
On Mon, Oct 30, 2006 at 10:59:38PM +0200, Eli Zaretskii wrote:
> > Date: Sun, 29 Oct 2006 23:11:13 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: gdb@sourceware.org
> >
> > I think that making GDB start to write temporary files in $PWD by
> > default would be extremely annoying.
>
> Okay, but can we at least make it read ./.gdb_history, if that exists?
I can see why that would be a good idea. Before I make any changes in
this area, I will definitely look into that and see if it's possible.
Or a simpler possibility: we could use .gdb_history as the default if
it exists and $HOME/.gdb_history otherwise.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-10-30 21:13 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
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 [this message]
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=20061030211347.GA22489@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--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