search for: untrace

...1:10 > xyplot(y ~ x) > trace(lattice:::print.trellis, exit=recover) [1] "print.trellis" Warning message: Assigning over the binding of symbol "print.trellis" in environment/package "lattice" in: .assignOverBinding(what, newFun, whereF) > xyplot(y ~ x) > untrace(lattice:::print.trellis) Error in untrace(lattice:::print.trellis) : Argument what should be the name of a function > Something isn't right. I see three possibilities. a. tracing something in a namespace is prohibited and I didn't get an error, instead I got a warning. b. tracing...

https://bugzilla.mindrot.org/show_bug.cgi?id=2584 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #6 from Damien Miller <djm at mindrot.org> --- Close all resolved bugs after 7.3p1 release

...I got no answer to my first mail, I suspect I did not formulate my question adequately, so I try again. In R, one can debug or trace a function 'foo' with debug(foo) or trace(foo), respectively. This leads to a special treatment of the function 'foo' until one enter undebug(foo) or untrace(foo). I would like to know if there is a convenient way to know at any time which are the function flagged with debug() or trace() in a R session. Thank you, Cheers, Philippe Grosjean ...........]<(({?<...............<?}))><............................... ) ) ) ) ) __...

...)) Error in getFunction(what, where = whereF) : no function "plot" found Okay, it's just an example that doesn't work. Let's try a simpler one, the first example from the ?trace man page: > trace(sum) > hist(stats::rnorm(100)) # shows about 3-4 calls to sum() > untrace(sum) No trace! In a clean session without the first error, things are fine: > trace(sum) > hist(stats::rnorm(100)) # shows about 3-4 calls to sum() trace: sum(2^(opts - 2)) trace: sum(2^(opts - 2)) trace: sum(2^(opts - 2)) trace: sum(counts) trace: sum(2^(opts - 2)) > untrace(sum) D...

I''m pleased to pass along news that the Mac OS X DTrace port has been updated in 10.5.3 to fix the issue that caused timer based probes not to fire in the presence of certain untraceable applications. http://blogs.sun.com/ahl/entry/apple_updates_dtrace A big thank you to the folks at Apple for addressing the problem. Adam -- Adam Leventhal, Fishworks http://blogs.sun.com/ahl

> On 28 Jun 2019, at 16:03 , Martin Maechler <maechler at stat.math.ethz.ch> wrote: > >>>>>> Henrik Bengtsson >>>>>> on Thu, 27 Jun 2019 16:00:39 -0700 writes: > >> Using: >> >> untrace(methods::conformMethod) >> at <- c(12,4,3,2) >> str(body(methods::conformMethod)[[at]]) >> ## language omittedSig <- omittedSig && (signature[omittedSig] != "missing") >> cc <- 0L >> trace(methods::conformMethod, tracer = quote({ >> cc...

Using: untrace(methods::conformMethod) at <- c(12,4,3,2) str(body(methods::conformMethod)[[at]]) ## language omittedSig <- omittedSig && (signature[omittedSig] != "missing") cc <- 0L trace(methods::conformMethod, tracer = quote({ cc <<- cc + 1L print(cc) if (cc == 31) { ##...

>>>>> Henrik Bengtsson >>>>> on Thu, 27 Jun 2019 16:00:39 -0700 writes: > Using: > > untrace(methods::conformMethod) > at <- c(12,4,3,2) > str(body(methods::conformMethod)[[at]]) > ## language omittedSig <- omittedSig && (signature[omittedSig] != "missing") > cc <- 0L > trace(methods::conformMethod, tracer = quote({ > cc <<- cc + 1L >...

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

...) trace(fun, quote(print("!!!"))) >> base::fun >> # Object with tracing code, class "functionWithTrace" >> # Original definition: >> # function() "hello" >> # >> # ## (to see the tracing code, look at body(object)) >> >> `untrace()` has the same behavior. >> >> This is inconsistent with how debug works : >> >> foo <- function() "hello" >> debug2 <- function(fun) debug(fun) >> debug2(foo) >> isdebugged(foo) >> # [1] TRUE >> >> This can be worked arou...

...ted : foo <- function() "hello" trace2 <- function(fun) trace(fun, quote(print("!!!"))) base::fun # Object with tracing code, class "functionWithTrace" # Original definition: # function() "hello" # # ## (to see the tracing code, look at body(object)) `untrace()` has the same behavior. This is inconsistent with how debug works : foo <- function() "hello" debug2 <- function(fun) debug(fun) debug2(foo) isdebugged(foo) # [1] TRUE This can be worked around by defining : trace2 <- function(fun) eval.parent(substitute(trace(fun, quote(pr...

...tes: > > On 28 Jun 2019, at 16:03 , Martin Maechler <maechler at stat.math.ethz.ch> wrote: > > > >>>>>> Henrik Bengtsson > >>>>>> on Thu, 27 Jun 2019 16:00:39 -0700 writes: > > > >> Using: > >> > >> untrace(methods::conformMethod) > >> at <- c(12,4,3,2) > >> str(body(methods::conformMethod)[[at]]) > >> ## language omittedSig <- omittedSig && (signature[omittedSig] != "missing") > >> cc <- 0L > >> trace(methods::conformMethod, trac...

...er <maechler at stat.math.ethz.ch> wrote: >> > >> >>>>>> Henrik Bengtsson >> >>>>>> on Thu, 27 Jun 2019 16:00:39 -0700 writes: >> > >> >> Using: >> >> >> >> untrace(methods::conformMethod) >> >> at <- c(12,4,3,2) >> >> str(body(methods::conformMethod)[[at]]) >> >> ## language omittedSig <- omittedSig && (signature[omittedSig] != "missing") >> >> cc <- 0L >> &gt...

....ethz.ch> wrote: ? ? >>> > ? ? >>> >>>>>> Henrik Bengtsson ? ? >>> >>>>>>? ? on Thu, 27 Jun 2019 16:00:39 -0700 writes: ? ? >>> > ? ? >>> >> Using: ? ? >>> >> ? ? >>> >> untrace(methods::conformMethod) ? ? >>> >> at <- c(12,4,3,2) ? ? >>> >> str(body(methods::conformMethod)[[at]]) ? ? >>> >> ## language omittedSig <- omittedSig && (signature[omittedSig] != "missing") ? ? >>> >> cc <- 0L...

I've found that reference class objects tend to behave like plain old environments wrt field access, unless a method on e.g. $<- is explicitly defined. Here is a code snippet: library(methods) Foo <- setRefClass("Foo") foo <- Foo$new() foo$a <- 2 # why does this succeed? not a valid field! ## set a silly $<- method setReplaceMethod("$", "Foo",

Hi Tomas, The doc indeed describes `what` as "the name, possibly quote()d, of a function to be traced or untraced". This is a good argument not to change the function and make it behave more like debug. However the doc also tells us "A call to trace allows you to insert debugging code (e.g., a call to browser or recover) at chosen places in any function" and "The trace function operates b...

...math.ethz.ch> wrote: >>> > >>> >>>>>> Henrik Bengtsson >>> >>>>>> on Thu, 27 Jun 2019 16:00:39 -0700 writes: >>> > >>> >> Using: >>> >> >>> >> untrace(methods::conformMethod) >>> >> at <- c(12,4,3,2) >>> >> str(body(methods::conformMethod)[[at]]) >>> >> ## language omittedSig <- omittedSig && (signature[omittedSig] != "missing") >>> >> cc <- 0L...

....ethz.ch> wrote: >>> > >>> >>>>>> Henrik Bengtsson >>> >>>>>> on Thu, 27 Jun 2019 16:00:39 -0700 writes: >>> > >>> >> Using: >>> >> >>> >> untrace(methods::conformMethod) >>> >> at <- c(12,4,3,2) >>> >> str(body(methods::conformMethod)[[at]]) >>> >> ## language omittedSig <- omittedSig && (signature[omittedSig] != "missing") >>> >> cc <- 0L...

..._PTRACE_H +#include <sys/ptrace.h> +#endif #ifdef HAVE_PRIV_H #include <priv.h> /* For setpflags() and __PROC_PROTECT */ #endif @@ -40,4 +43,9 @@ platform_disable_tracing(int strict) if (setpflags(__PROC_PROTECT, 1) != 0 && strict) fatal("unable to make the process untraceable"); #endif +#ifdef PT_DENY_ATTACH + /* Mac OS X */ + if (ptrace(PT_DENY_ATTACH, 0, 0, 0) == -1 && strict) + fatal("unable to set PT_DENY_ATTACH"); +#endif } -- Darren Tucker (dtucker at zip.com.au) GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860 37F4 9357 ECEF 11EA A6FA...

...ing both problems: 1. Refusal to join the domain. I modified well the key in my Windows, I was kind enough to change domain. That recognized it because I fell at request of account of the domain samba. But at the time of entering my root and its password, I have the error message: "name of untraceable user ". The root account exists well. But on the other hand not the account of the machine. If I enter well the machine the users samba ( Adduser then smbpasswd), I manage to enter the domain. Nevertheless, on my smb.conf, I indeed have this: add machine script = /srv/samba/addmachine.sh...