similar to: debug package in R 2.4.0

Dear useRs, I am experiencing very strange error with Mark Bravington's package "debug". I haven't seen them before. Here is the sample session > library(debug) Loading required package: mvbutils MVBUTILS: no "tasks" vector found in ROOT Loading required package: tcltk Loading Tcl/Tk interface ... done > x<-function() return(1) > mtrace(x) > x() Error

Hello Users: I'm using R version 2.0.1, and having problems with RODBC. Everything works fine when I use Rgui, but when I try to use Rterm and issue the commands library(RODBC) con <- odbcConnect("MySQL", "test") I get the following error: Error in sqlQuery(con, str) : first argument is not an open RODBC channel In addition: Warning messages:

Hi, everyone. I am using a fair amount of closures in my code. Problem i am experiencing is i cannot figure out how to mtrace functions defined within a function. There must be some way to name such function for mtrace to see it and let me step into it. For example, say i have code mymodel<-function(){ data<-numeric(0) build<-function(){ data<<-1 } m<-list()

A number of users have spotted a terminal problem with the 'debug' package under R2.4.0, along the lines of > mtrace(x) > x() Error in attr(value, "row.names") <- rlabs : row names must be 'character' or 'integer', not 'double' This arose from a bug in 'rbind.data.frame' in R2.4.0 itself. The bug is fixed in R2.4.0 patched, so the

Hello, pointed to the article "Debugging Without (Too Many) Tears" of Mark Bravington in Rnews Vol 3/3, December 2003 there is a package mvbutils mentioned. So I started to install this package from within R > install.package(mvbutils) I receive an error essage that this package is not found! Is due to a merge,removal or rename of this package? When I try to follow this

How do you debug methods of a reference class? I've been using mtrace, which is excellent, but i cannot figure out how to mtrace a reference class method. Maybe there is some other way to debug these, for example with ordinary trace? for now i am only able to use options(error=recover), which is not giving me idea where exactly in the code i am once i am stopped on an error. -- View this

I would like to suggest a modification to the make.names() function. The current implementation has two problems: 1. It doesn't check if a name matches an R keyword (like "function"). 2. The uniqueness algorithm is not invariant to concatenation. In other words, make.names(c("a","a","a"),unique=T) !=

I would like to suggest a modification to the make.names() function. The current implementation has two problems: 1. It doesn't check if a name matches an R keyword (like "function"). 2. The uniqueness algorithm is not invariant to concatenation. In other words, make.names(c("a","a","a"),unique=T) !=

I have a Gamatronic Smart Compact 750. I have it connected to my linux machine via serial cable and am running nut 2.0.3. There is no interruption in power, but the ups is reporting OB (on battery). Is there a configuration option I am missing? The relevant ups.conf entry is: [Gamatronic] port = /dev/ttyS1 desc = "Home Gamatronic UPS" driver = genericups

Hello I need some help in figuring Bravington’s debugger out. Ok I have 2 functions, fun1 and fun2 saved in a ASCII file say filename is funs. Fun1 has a loop which calls fun2, fun2 has a loop which fails and I need to find out the value of the variables of the fun2 and fun1 loops at the specific iteration that fails. Both fun1 and fun2 loops will iterate thousands of times so line by line debug

I would like to be able to trace execution into calls below the current function, or to follow execution as calls return. This is roughly the distinction between "step" and "next" in many debuggers. I would also like to be able to switch to a location further up the call stack than the location at which I enter the debugger, to see the context of the current operations. Are

Dear list, I received the response below from the package author of 'debug'. I post it to the list, with Mark's approval, in case it is useful to others too. Regards, Matthew -----Original Message----- From: Mark.Bravington at csiro.au [mailto:Mark.Bravington at csiro.au] Sent: 22 October 2006 23:53 To: Matthew Dowle Cc: Mark.Bravington at csiro.au Subject: RE: Debug package

Hi all, I am using "mtrace" malloc debugging utility to trace memory leaks in my application. I followed following steps: 1. Added mtrace() function in the beginning of my main function. 2. exported the MALLOC_TRACE environment variable. $ export MALLOC_TRACE=memory.log 3. Run the program 4. trace the program for memory leaks. $ mtrace <myprogram> $MALLOC_TRACE But In

# Your mailer is set to "none" (default on Windows), # hence we cannot send the bug report directly from R. # Please copy the bug report (after finishing it) to # your favorite email program and send it to # # r-bugs@r-project.org # ###################################################### > x <- rnorm(10) > y <- 1:10 > xyplot(y ~ x) >

Hello I am trying to follow the instruction in README.debug on how to debug a code I wrote, so since it only shows the steps on how to debug a built in function and not a code in an *.R file, so ok, let me do this and maybe later I can find out how to code my code in filename.R. now > library(debug) Loading required package: mvbutils MVBUTILS: no "tasks" vector found in ROOT Loading

I don't know the right computer science words for this question, I'm afraid. Apology in advance. How do you find your way around in somebody else's code? If the user runs a specific command, and wants to know how the data is managed until the result is returned, what to do ? I've tried this manually with tools like mtrace and browser. This is a bit frustrating because the

Hi all, Since three month ago I started working with R professionally, I never did it before, so I am such a newbie. I am having some problems using the 'debug' package. I love this package, but most of the times I wanna use it it just fails :P When typing at prompt 'mtrace(myfunct)' most of the times I get the following error: "Error in x[[i]] : subscript out of

This is a question about namespaces and assignment. It's occasioned because one of my functions stopped working at about R1.6 with the arrival of 'namespace:base', and I'm anxious to find out what will happen when 1.7 arrives. But the question might be of more general relevance (hence my desire to get it in before "lockdown" on 9th April). I have a function

I use windows xp. When trying to use the function mtrace from package debug the window that should open with the function to be debugged do not show any text at all. It shows only a part of my desktop. Does anyone know why. Is there any imcompatibility between windows xp and debug package. Thanks in advance. Enio Jelihovschi [[alternative HTML version deleted]]

When attempting to merge 3 data frames, one of which has fewer columns than the others, rbind.data.frame correctly refuses to perform the bind. However, the error message given is a bit obscure due to a logical bug in the match.names() internal function to rbind.data.frame. Illustration: ## Three data frames with same column variable names: > foo <- data.frame(v1 = c('a',