similar to: Missing objects using dump.frames for post-mortem debugging of crashed batch jobs. Bug or gap in documentation?

Displaying 20 results from an estimated 9000 matches similar to: "Missing objects using dump.frames for post-mortem debugging of crashed batch jobs. Bug or gap in documentation?"

2016 Nov 15
2
Missing objects using dump.frames for post-mortem debugging of crashed batch jobs. Bug or gap in documentation?
Martin, thanks for the good news and sorry for wasting your (and others time) by not doing my homework and query bugzilla first (lesson learned! ). I have tested the new implementation from R-devel and observe a semantic difference when playing with the parameters: # Test script 1 g <- "global" f <- function(p) { l <- "local" dump.frames() }
2016 Nov 15
0
Missing objects using dump.frames for post-mortem debugging of crashed batch jobs. Bug or gap in documentation?
>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>> on Tue, 15 Nov 2016 01:15:46 +0100 writes: > Martin, thanks for the good news and sorry for wasting your (and others > time) by not doing my homework and query bugzilla first (lesson learned! > ). > > I have tested the new implementation from R-devel and observe a semantic >
2016 Nov 14
0
Missing objects using dump.frames for post-mortem debugging of crashed batch jobs. Bug or gap in documentation?
>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>> on Sun, 13 Nov 2016 13:11:38 +0100 writes: > Dear R friends, to allow post-mortem debugging In my > Rscript based batch jobs I use > tryCatch( <R expression>, error = function(e) { > dump.frames(to.file = TRUE) }) > to write the called frames into a
2023 Apr 16
2
Unique ID for conditions to supress/rethrow selected conditions?
I am the author of the *tryCatchLog* package and want to - suppress selected conditions (warnings and messages) - rethrow selected conditions (e.g a specific warning as a message or to "rename" the condition text). I could not find any reliable unique identifier for each possible condition - that (base) R throws - that 3rd-party packages can throw (out of scope here). Is there any
2016 Feb 23
4
iconv to UTF-16 encoding produces error due to embedded nulls (write.table with fileEncoding param)
>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>> on Mon, 22 Feb 2016 18:45:59 +0100 writes: > Dear R developers > I think I have found a bug that can be reproduced with two lines of code > and I am very thankful to get your first assessment or feed-back on my > report. > If this is the wrong mailing list or I
2016 Feb 24
2
iconv to UTF-16 encoding produces error due to embedded nulls (write.table with fileEncoding param)
On 23/02/2016 7:06 AM, Mikko Korpela wrote: > On 23.02.2016 11:37, Martin Maechler wrote: >>>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>>>> on Mon, 22 Feb 2016 18:45:59 +0100 writes: >> >> > Dear R developers >> > I think I have found a bug that can be reproduced with two lines of code
2016 Feb 25
2
iconv to UTF-16 encoding produces error due to embedded nulls (write.table with fileEncoding param)
On 23.02.2016 14:06, Mikko Korpela wrote: > On 23.02.2016 11:37, Martin Maechler wrote: >>>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>>>> on Mon, 22 Feb 2016 18:45:59 +0100 writes: >> >> > Dear R developers >> > I think I have found a bug that can be reproduced with two lines of code >>
2016 Feb 16
2
iconv to UTF-16 encoding produces error due to embedded nulls (write.table with fileEncoding param)
If I execute the code from the "?write.table" examples section x <- data.frame(a = I("a \" quote"), b = pi) # (ommited code) write.csv(x, file = "foo.csv", fileEncoding = "UTF-16LE") the resulting CSV file has a size of 6 bytes which is too short (truncated): """,3 The problem seems to be the iconv function:
2016 Feb 23
1
iconv to UTF-16 encoding produces error due to embedded nulls (write.table with fileEncoding param)
Excellent analysis, thank you both for the quick reply! Is there anything I can do to get the bug fixed in the next version of R (e. g. filing a bug report at https://bugs.r-project.org/bugzilla3/)? On Tue, 2016-02-23 at 14:06 +0200, Mikko Korpela wrote: > On 23.02.2016 11:37, Martin Maechler wrote: > >>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >
2016 Feb 24
2
iconv to UTF-16 encoding produces error due to embedded nulls (write.table with fileEncoding param)
On 24/02/2016 9:55 AM, Mikko Korpela wrote: > On 24.02.2016 15:47, Duncan Murdoch wrote: >> On 23/02/2016 7:06 AM, Mikko Korpela wrote: >>> On 23.02.2016 11:37, Martin Maechler wrote: >>>>>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>>>>>> on Mon, 22 Feb 2016 18:45:59 +0100 writes: >>>>
2016 Feb 29
1
iconv to UTF-16 encoding produces error due to embedded nulls (write.table with fileEncoding param)
I have just committed your first patch (the strlen() replacement) to R-devel, and will soon put it in R-patched as well. I wont have time to look at this again before the 3.2.4 release, so your file.show() patch isn't going to make it unless someone else gets to it. There's still a faint chance that I'll do more in R-devel before 3.3.0, but I think it's best if there were bug
2019 Sep 29
2
typeof(getOption("warn")) is "integer" instead of "double" in R unstable (2019-09-27 r77229)? Reproducible?
Thanks a lot for pointing out the reason (and yes, I am testing quite to stringent in this case - it's my old testing disease ;-) For other readers: The R-devel NEWS is a good source to find possible change reasons: https://stat.ethz.ch/R-manual/R-devel/doc/html/NEWS.html On Sun, 2019-09-29 at 08:33 -0400, Duncan Murdoch wrote: > On 29/09/2019 7:55 a.m., nospam at altfeld-im.de wrote:
2011 Oct 11
0
Post Mortem 1 huge grafical issues
Hi everybody, The Game Post Mortem 1 is unplayable in my wine. This is causing by huge grafical issues. Items are not correct drawn and People "flashes". Here is waht the Console says: Code: pingi at 16L:/media/32GB-usb3/Spiel_1/Programme/Microids/Post Mortem$ wine "Post Mortem.exe" fixme:win:EnumDisplayDevicesW ((null),0,0x32ee4c,0x00000000), stub!
2006 Mar 10
2
appending objects to a file created by save()
Hi, I've been slowly transitioning to saving sets of objects for a project using save() rather than cluttering my workspace and then doing save.image() However, sometimes after I have done say: save(x,y,z, file='work.Rda') and I reload it a little later and I see that I also want to save object p. Currently I need to do: save(x,y,z,p, file='work.Rda') Is there any way
2014 Mar 21
1
windigo post-mortem
ESET recently published an interesting post-mortem of the so-called "Operation Windigo" malware campaign [1]. OpenSSH backdoors (codename Linux/Ebury), described by ESET last month [2], are a key component of Windigo's attack surface. --mancha [1] http://www.welivesecurity.com/wp-content/uploads/2014/03/operation_windigo.pdf [2]
2004 Sep 05
0
[LLVMdev] POST MORTEM: llvm-test changes
> Bash 2.05b on Linux handles this fine. I was asking what > your "default" system shell is on FreeBSD. Probably /bin/sh, right? > Perhaps you can: > > SHELL=/usr/bin/bash ; export SHELL > > in your script below just before it runs NightlyTest.pl? I'm not sure if > that will work or not. I have: SHELL=/bin/tcsh sh, csh, tcsh not support nested () OK, root
2004 Sep 09
0
[LLVMdev] POST MORTEM: llvm-test changes
On Sun, 05 Sep 2004 14:02:26 -0700 Reid Spencer <reid at x10sys.com> wrote: > > Assertion failed: ((FieldSizeTree != NULL_TREE) && "Struct/Union member of unknown length!"), function llvm_expand_constructor_elements, file ../../src/gcc/llvm-expand.c, line 3791. > > /usr/home/llvm/obj/../test/Regression/CFrontend/2004-01-01-UnknownInitSize.c:11: internal compiler
2004 Sep 10
0
[LLVMdev] POST MORTEM: llvm-test changes
On Thu, 9 Sep 2004 08:52:10 -0700 Jeff Cohen <jeffc at jolt-lang.org> wrote: > > I haven't got around to this yet but I will. The odds are good the > > problem is in a BSD system header file so I need to capture the > > preprocessed source. > > I guess not... the file 2004-01-01-UnknownInitSize.c does not include > anything else, so there is no preprocessed
2009 Sep 14
1
loading a package .Rda file at package load time
Hi, I have seen the answer to this sometime before but I just can't find it again - pointers appreciated. I have a package that contains some data.frames saved as .Rda files in the data/ directory. When the package is loaded I would like to have them be available in the workspace (without the user having to explicitly load them using data(...)). If my package does not use a NAMESPACE, I can
2004 Sep 09
2
[LLVMdev] POST MORTEM: llvm-test changes
> I haven't got around to this yet but I will. The odds are good the > problem is in a BSD system header file so I need to capture the > preprocessed source. I guess not... the file 2004-01-01-UnknownInitSize.c does not include anything else, so there is no preprocessed source to capture...