search for: undebug

debugonce() sets a different flag (RSTEP), and this is not queried by isdebugged(), and it is also not unset by undebug(). Is this expected? If yes, is there a way to query and unset the RSTEP flag from R code? ? f <- function() { } ? debugonce(f) ? isdebugged(f) [1] FALSE ? undebug(f) Warning message: In undebug(f) : argument is not being debugged ? f() debugging in: f() debug at #1: { } Browse[2]>

...h callbacks are "debugged" currently, either via `debug()` or `debugonce()`. Gabor > Best, > Tomas > On 04/28/2018 01:57 PM, G?bor Cs?rdi wrote: > > debugonce() sets a different flag (RSTEP), and this is not queried by > > isdebugged(), and it is also not unset by undebug(). > > > > Is this expected? If yes, is there a way to query and unset the RSTEP flag > > from R code? > > > > ? f <- function() { } > > ? debugonce(f) > > ? isdebugged(f) > > [1] FALSE > > > > ? undebug(f) > > Warning message: &g...

...llo all, Since 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 ...........]<(({?<...............<?}))><............................... ) ) ) )...

...as.kalibera at gmail.com> > wrote: > [...] >> Do you have a good use case when it would be useful to query/unset the >> mark for debugonce? > Well, I suppose the same use cases when it is useful to query/unset the > other debug > mark. I asked because the use cases for undebug/debugonce I can think of do not apply. undebug() is needed once you have run a function through a debugger few times and figured out there is no bug there but you want to run again debugging from somewhere else. It is like deleting a breakpoint in say gdb. undebugonce() would make no sense in t...

debug(fun) marks "fun" for debugging, it makes sure that whenever "fun" is called, the debugger is entered undebug(fun) removes this mark; it won't stop any current debugging of that function isdebugged(fun) tells whether this mark is set or not; it does not tell whether "fun" is currently running in a debugger/browser debugonce(func) adds a different mark to the function, one that makes sure...

...4 This works because when we build LLVM with assert we explicitly disable NDEBUG: if( LLVM_ENABLE_ASSERTIONS ) […] # On non-Debug builds cmake automatically defines NDEBUG, so we # explicitly undefine it: if( NOT uppercase_CMAKE_BUILD_TYPE STREQUAL "DEBUG" ) add_definitions( -UNDEBUG ) If we use this header in a different project and thus, with potentially different rules for macro definitions, the compiler complains with error: use of undeclared identifier ‘Poisoned' I think the right thing to do is to fix the code to work without the special way of setting the macros,...

I have some troublesome numbers that I would like to capture the SIP dialogue when I am calling them. When I am about to dial the number, is there any way to turn on SIP debugging in the dial plan before I make the call? (and turn it off after the call is completed?) -------------- next part -------------- An HTML attachment was scrubbed... URL:

Frits van Bommel <fvbommel at wxs.nl> writes: > Paul Melis wrote: >> Just checked: yup, there's plenty of assert()'s in the headers, so >> -D_DEBUG will keep those alive. >> >> Interestingly, when configuring with --enable-optimized and >> --disable-assertions the resulting compilation calls itself a >> "Release-Asserts build" while

...Thanks! I think it might be nice to make this a bit more consistent with Makefile.config. I'd suggest... - use LLVM_DISABLE_ASSERTIONS instead of LLVM_ENABLE_ASSERTS - have it default to OFF (so assertions are enabled) always - compile with -DNDEBUG if assertions are off -- I don't think -UNDEBUG has any effect, because NDEBUG won't have been defined in the first place Thanks, Jay.

...The fact that the configure/make build does not follow this policy caused some surprise among the LLVM developers and users on the past. So it is the configure/make build the one that needs to be fixed :-) > - compile with -DNDEBUG if assertions are off -- Good catch! > I don't think -UNDEBUG has any effect, because NDEBUG won't have been > defined in the first place Right. For Release builds, cmake automatically defines NDEBUG. -- Óscar

...-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wno-maybe-uninitialized -Wdelete-non-virtual-dtor -Wno-comment -Werror=date-time -std=c++11 -ffunction-sections -fdata-sections -fno-common -Woverloaded-virtual -fno-strict-aliasing -O3 -fPIC -UNDEBUG -fno-exceptions -fno-rtti -MMD -MT tools/clang/tools/libclang/CMakeFiles/libclang.dir/CIndex.cpp.o -MF tools/clang/tools/libclang/CMakeFiles/libclang.dir/CIndex.cpp.o.d -o tools/clang/tools/libclang/CMakeFiles/libclang.dir/CIndex.cpp.o -c /home/aghadge/build/llvm/llvm_build.4.0/llvm/tools/clang/to...

Hi, for filing a GCC v8.2.0 bug in Debian/buster AMD64 the Debian/GCC mainatiners want two things... [ FULL CMAKE LINE ] How do I configure this in the LLVM/Clang build? Can I set an option of cmake? [ PREPROCESSED SOURCE FILES ] How and where do I get the preprocessed source? Do I need to set options for this in my build-script? My build-script is attached. Thanks in advance. Regards, -

...-Werror=date-time -std=c++11 -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wno-maybe-uninitialized -Wno-class-memaccess -Wdelete-non-virtual-dtor -Wno-comment -fdiagnostics-color -ffunction-sections -fdata-sections -O3 -UNDEBUG -fno-exceptions -fno-rtti -MD -MT lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o -MF lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o.d -o lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o -c /home/sdi/src/llvm-toolchain/llvm/lib/Bitcode...

...build LLVM with assert we explicitly disable NDEBUG: > if( LLVM_ENABLE_ASSERTIONS ) > […] > # On non-Debug builds cmake automatically defines NDEBUG, so we > # explicitly undefine it: > if( NOT uppercase_CMAKE_BUILD_TYPE STREQUAL "DEBUG" ) > add_definitions( -UNDEBUG ) > > If we use this header in a different project and thus, with potentially different rules for macro definitions, the compiler complains with > error: use of undeclared identifier ‘Poisoned' > > I think the right thing to do is to fix the code to work without the special w...

...t;>>>> -Wno-missing-field-initializers -pedantic -Wno-long-long >>>>>> -Wno-maybe-uninitialized -Wno-class-memaccess >>>>>> -Wdelete-non-virtual-dtor -Wno-comment -fdiagnostics-color >>>>>> -ffunction-sections -fdata-sections -O3 -UNDEBUG -fno-exceptions >>>>>> -fno-rtti -MD -MT >>>>>> lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o >>>>>> -MF lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o.d >>>>>> -o lib/Bitcode/Reade...

...++11 -Wall -Wextra > -Wno-unused-parameter -Wwrite-strings -Wcast-qual > -Wno-missing-field-initializers -pedantic -Wno-long-long > -Wno-maybe-uninitialized -Wno-class-memaccess > -Wdelete-non-virtual-dtor -Wno-comment -fdiagnostics-color > -ffunction-sections -fdata-sections -O3 -UNDEBUG -fno-exceptions > -fno-rtti -MD -MT > lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o > -MF lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o.d > -o lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o > -c /home/sdi/src/llvm-t...

...from: NULL Browse[1]> n n debug: print(i) Browse[1]> Q Q # remove browser(), debug() is still there > for (i in seq(5)) { print(i) } for (i in seq(5)) { print(i) } debug: i Browse[1]> Q Q My guess is that when I was stepping through some function got flagged for debugging. I tried to undebug "for", but that didn't work. This is R.1.5.0 on RedHat Linux 7.1 Any suggestion will be appreciated. Thanks, Vadim P.S. I thought it might be useful to have a function that lists all functions currently flagged for debugging. -------------------------------------------------- DI...

...uot; Browse[1]> debug: Sweave("test.rnw", driver = RweaveHTML) Browse[1]> x [1] "ABC" Browse[1]> y [1] 1 2 3 4 5 Browse[1]> Writing to file test.html Processing code chunks ... 1 : term html Error: chunk 1 Error in print(y) : object "y" not found > >undebug(f1) > > y <- 1:5 > x <- "ABC" > > >ls() [1] "f1" "x" "y" > Sweave("test.rnw", driver=RweaveHTML) Writing to file test.html Processing code chunks ... 1 : term html file test.html is completed > >R.Version()...

...write-strings -Wcast-qual >>>> -Wno-missing-field-initializers -pedantic -Wno-long-long >>>> -Wno-maybe-uninitialized -Wno-class-memaccess >>>> -Wdelete-non-virtual-dtor -Wno-comment -fdiagnostics-color >>>> -ffunction-sections -fdata-sections -O3 -UNDEBUG -fno-exceptions >>>> -fno-rtti -MD -MT >>>> lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o >>>> -MF lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o.d >>>> -o lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/M...

...ction(...) as.IDate(NextMethod()) ] Lastly, it appears that as.Date.IDate is called, which is causing the type conversion: debug(data.table:::as.Date.IDate) rbind(DF, DF) # launches debugger x # [1] "2019-05-26" <-- singleton, so apparently applied to DF$date, not c(DF$date, DF$date) undebug(data.table:::as.Date.IDate) I can't really wrap my head around why as.Date is being called here, and even allowing that, why the end result is still the original class [ class(rbind(DF, DF)$date) == c('IDate', 'Date') ] So, I'm beginning to think this might be a bug. Am I...