From pleydell at supagro.inra.fr  Fri Sep  4 18:11:22 2009
From: pleydell at supagro.inra.fr (pleydell at supagro.inra.fr)
Date: Fri, 04 Sep 2009 18:11:22 +0200
Subject: [Rd] enabling core dumps
In-Reply-To: <20090904174842.rj5qh6kk93k8wg0k@web.supagro.inra.fr>
References: <20090904173944.et305vc9gon4480c@web.supagro.inra.fr>
	<20090904174842.rj5qh6kk93k8wg0k@web.supagro.inra.fr>
Message-ID: <20090904181122.15h3os7s249w0o04@web.supagro.inra.fr>

> not really answering your question, but I find it more useful to
>
>  R -d gdb
>
> or
>
>  R -d gdb -f test.R
>
> where test.R reproduces the bug in some minimal code. A variant is
>
>  R -d valgrind -f test.R
>
> if the memory problem is not easy to spot.

Thanks for your reply Martin

Yes, I have used that route before, I have also been playing with the 
emacs "M-x
gdb" option as describe in the R FAQ. But having no first hand 
expertience with
core dumps I am curious why you prefer the -d flag route. Perhaps I'm 
wrong but
I thought examining a core dump enables you to backtrace from the 
moment things
went wrong, this seems to be a useful trick to have...

... if you manage to enable the core dump option that is.

cheers
David



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