From pleydell at supagro.inra.fr  Tue Sep 29 19:20:54 2009
From: pleydell at supagro.inra.fr (pleydell at supagro.inra.fr)
Date: Tue, 29 Sep 2009 19:20:54 +0200
Subject: [Rd] enabling core dumps
In-Reply-To: <20090923160726.qtfgqgygmbk0s44w@web.supagro.inra.fr>
References: <20090904173944.et305vc9gon4480c@web.supagro.inra.fr>
	<20090904174842.rj5qh6kk93k8wg0k@web.supagro.inra.fr>
	<20090904181122.15h3os7s249w0o04@web.supagro.inra.fr>
	<4AA14290.1060401@fhcrc.org>
	<20090923160726.qtfgqgygmbk0s44w@web.supagro.inra.fr>
Message-ID: <20090929192054.hgw8mw1egqsg0o0s@web.supagro.inra.fr>

> ... If I launch gdb this way I don't have any means to navigate through
> previously executed gdb lines using M-p and M-n, but following a
> (gdb) run
> or
> (gdb) continue
> I can use M-p and M-n to recall previous R commands
>
> If I launch gdb in other ways M-p and M-n function as expected. I 
> suppose there
> is a confusion between gdb's M-p and ESS's M-p so that M-p only functions in
> the ESS session.
>
> I quite like running gdb using R's -d flag, but not being able to navigate
> through the line history is sub-optimal. I'd be interested to hear if other
> people running gdb this way encountered this problem and how they 
> resolved it.

This had a one line solution (section 19.3, page 216, gdb manual)

gdb> set history save on



[Rd] enabling core dumps
pleydell at supagro.inra.fr