From Friedrich.Leisch@ci.tuwien.ac.at  Fri Jan 16 15:42:08 1998
From: Friedrich.Leisch@ci.tuwien.ac.at (Friedrich Leisch)
Date: Fri, 16 Jan 1998 16:42:08 +0100
Subject: debugging dynamically loaded code
In-Reply-To: <6rbtxdwzwx.fsf@franz.stat.wisc.edu>
References: <199801151113.MAA01121@galadriel.ci.tuwien.ac.at>
 <6rbtxdwzwx.fsf@franz.stat.wisc.edu>
Message-ID: <199801161542.QAA28822@galadriel.ci.tuwien.ac.at>

>>>>> On 15 Jan 1998 08:54:38 -0600,
>>>>> Douglas Bates (DB) wrote:

DB> The secret of symbolic debugging of dynamically loaded code is to
DB>  - Call the debugger on the R executable.  Since I do this within
DB>    emacs, I don't use the "R gdb" facility, I symbolically link the
DB>    R.binary file into the directory with my code and call the debugger 
DB>    through M-x gdb.
DB>  - Set the environment variables that the $RHOME/bin/R script would.
DB>  - Start the R program.
DB>  - At the R prompt, use dyn.load() to load your library.
DB>  - Send an interrupt signal.  Inside of gud mode in emacs, I think you 
DB>    send C-C C-C.  This will put you back to the debugger prompt.
DB>  - Set the breakpoints in your code.
DB>  - Continue execution of R by typing "signal 0<ret>".

Thanks a lot ... I did not know about the interrupt signal before
inserting a breakpoint etc.

Best,
Fritz

PS: Thanks also for the S_compat stuff ... now I've got a first
version of [mpf]da up and running ... now it's only the buggy
model.matrix code that troubles me ... but that's a different story!

-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-devel-request@stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._


debugging dynamically loaded code
Friedrich Leisch