On 11/16/2007 9:48 AM, Yan Wong wrote:
> On 16 Nov 2007, at 14:16, Duncan Murdoch wrote:
>
>> On 11/16/2007 6:58 AM, Yan Wong wrote:
>>> Hi,
>>> I can't seem to find a way to do this (i.e. interrupt a routine at
>>> an arbitrary time during its run, then step into it using the
>>> debugger).
On 16 Nov 2007, at 15:05, Gabor Grothendieck wrote:
> Try this:
>
> f <- function() {
>for(i in 1:1000) {
> if (i == 50) browser()
> print(i)
> }
> }
>
> # enters debugger when i is 50.
> # n/c/Q will step one statement/continue/Quit respectively
> f()
Thanks. The problem is that
Try this:
f <- function() {
for(i in 1:1000) {
if (i == 50) browser()
print(i)
}
}
# enters debugger when i is 50.
# n/c/Q will step one statement/continue/Quit respectively
f()
On Nov 16, 2007 6:58 AM, Yan Wong <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have an R program which takes
On 16 Nov 2007, at 14:16, Duncan Murdoch wrote:
> On 11/16/2007 6:58 AM, Yan Wong wrote:
>> Hi,
>> I can't seem to find a way to do this (i.e. interrupt a routine at
>> an arbitrary time during its run, then step into it using the
>> debugger).
>
> If you prepare in advance by using options(
On 11/16/2007 6:58 AM, Yan Wong wrote:
> Hi,
>
> I have an R program which takes several days to run, and sometimes
> hangs while running, presumably stuck in some sort of loop within a
> package function. I don't know where in the program code it is
> hanging: it is likely to be within a ro
Hi,
I have an R program which takes several days to run, and sometimes
hangs while running, presumably stuck in some sort of loop within a
package function. I don't know where in the program code it is
hanging: it is likely to be within a routine that is iterated many
hundreds of thousands
6 matches
Mail list logo
