Displaying 20 results from an estimated 1000 matches similar to: "read.table problem on Linux/Alpha (seg faults caused by isspace(R_EOF)) (PR#303)"
2023 Feb 11
1
scan(..., skip=1e11): infinite loop; cannot interrupt
On Fri, 10 Feb 2023 23:38:55 -0600
Spencer Graves <spencer.graves at prodsyse.com> wrote:
> I have a 4.54 GB file that I'm trying to read in chunks using
> "scan(..., skip=__)". It works as expected for small values of
> "skip" but goes into an infinite loop for "skip=1e11" and similar
> large values of skip: I cannot even interrupt it; I
2023 Mar 13
0
scan(..., skip=1e11): infinite loop; cannot interrupt
With
?if?(!j--)?{
?????R_CheckUserInterrupt();
?????j?=?10000;
?}
as?in?current?R?devel?(r83976),?j goes negative (-1) and interrupt is checked every 10001 instead of 10000. I?prefer
?if?(!--j)?{
?????R_CheckUserInterrupt();
?????j?=?10000;
?}
.
In?current?R?devel?(r83976),?if?EOF?is?reached,?the?outer?loop?keeps?going,?i?keeps?incrementing?until?nskip.
2023 Feb 11
1
scan(..., skip=1e11): infinite loop; cannot interrupt
Hello, All:
I have a 4.54 GB file that I'm trying to read in chunks using
"scan(..., skip=__)". It works as expected for small values of "skip"
but goes into an infinite loop for "skip=1e11" and similar large values
of skip: I cannot even interrupt it; I must kill R. Below please find
sessionInfo() with a toy example.
My real problem is a large
2003 Nov 11
4
isspace() and other ctype.h functions
Hm, finally subscribed here, forgot to...
Anyway, I'm using klibc in udev and have added some needed functions
(like ftruncate and vsyslog). Should I post the patches here before
commiting them to the cvs tree?
Also, it looks like ctype.h has a off-by-one bug. isspace(' ') returns
0 right now, but if you change the function from:
__ctype_inline int isspace(int __c)
{
return
1999 Mar 25
4
readline() (PR#147)
Dear R developers,
I have found the following bug with readline() in R 0.63.3:
if you execute the menu-function and then the readline() function, then
readline() prompts "Selection:"
> a <- readline()
hello
> a
[1] "hallo"
> a <- menu(c("a", "b"), title="bitte:")
bitte:
1:a
2:b
Selection: 2
> a <- readline()
Selection:
2016 Jun 16
1
[PATCH] mllib: Add isspace, triml, trimr and trim functions.
---
mllib/common_utils.ml | 29 +++++++++++++++++++++++++++++
mllib/common_utils.mli | 8 ++++++++
2 files changed, 37 insertions(+)
diff --git a/mllib/common_utils.ml b/mllib/common_utils.ml
index 64bf3d3..34e1285 100644
--- a/mllib/common_utils.ml
+++ b/mllib/common_utils.ml
@@ -49,6 +49,35 @@ module String = struct
and len = length str in
len >= sufflen && sub str
2012 Jan 13
0
WISHLIST: Be able to timeout readline()/stdin via setTimeLimit in all consoles
Hi.
WISHLIST:
Regardless on console, I'd like to be able to timeout a call to
readline()/file("stdin", blocking=TRUE) via setTimeLimit.
OBSERVATION:
On Windows Rterm as well as plain R on Linux, setTimeLimit() does not
momentarily interrupt from stdin, but only after hitting RETURN. A
few examples:
timeout00 <- function() {
setTimeLimit(elapsed=5);
Sys.sleep(10);
}
2009 Mar 20
2
Why does the lexical analyzer drop comments ?
It happens in the token function in gram.c:
c = SkipSpace();
if (c == '#') c = SkipComment();
and then SkipComment goes like that:
static int SkipComment(void)
{
int c;
while ((c = xxgetc()) != '\n' && c != R_EOF) ;
if (c == R_EOF) EndOfFile = 2;
return c;
}
which effectively drops comments.
Would it be possible to keep the information
2004 Jun 30
2
Slow IO: was [R] naive question
I believe IO in R is slow because of the way it is implemented, not
because it has to do some extra work for the user.
I compared scan() with 'what' argument set (which is, AFAIK, is the
fastest way to read a CSV file) to an equivalent C code. It turned out
to be 20 - 50 times slower.
I can see at least two main reasons why R's IO is so slow (I didn't
profile this though):
A) it
2015 Sep 21
5
segfault with readDCF on R 3.1.2 on AIX 6.1 when using install.packages
Hi,
Note that one significant change to read.dcf() that happened since R
3.0.2 is the addition of support for arbitrary long lines (commit
63281), which never worked:
dcf <- paste(c("aa: ", rep(letters, length.out=10000)), collapse="")
writeLines(dcf, "test.dcf")
nchar(read.dcf("test.dcf"))
# aa
# [1,] 8186
The culprit being line
2002 Aug 02
3
[Bug 377] New: Reduce compiler warnings. Use unsigned args to the ctype.h is*() macros.
http://bugzilla.mindrot.org/show_bug.cgi?id=377
Summary: Reduce compiler warnings. Use unsigned args to the
ctype.h is*() macros.
Product: Portable OpenSSH
Version: -current
Platform: Sparc
OS/Version: Solaris
Status: NEW
Severity: trivial
Priority: P2
Component: Miscellaneous
2008 Aug 19
1
[patch] fix to ForceCommand to support additional arguments to internal-sftp
Hi,
This patch makes things like ForceCommand internal-sftp -l INFO work
(current code in 5.1 would just end the session). Please consider for
inclusion into mainline.
Michael.
--- /var/tmp/session.c 2008-08-18 21:07:10.000000000 -0700
+++ session.c 2008-08-18 21:12:51.000000000 -0700
@@ -781,7 +781,7 @@
if (options.adm_forced_command) {
original_command = command;
2009 Jul 07
1
Non-standard conformant usage of ctype functions
Hi,
Per the definitions of the ctype functions in POSIX-1.2008 "the c
argument is an int, the value of which the application shall ensure is a
character representable as an unsigned char or equal to the value of the
macro EOF. If the argument has any other value, the behavior is
undefined."
For obvious reasons this results in problems if you use signed char
variables as parameters in
2009 Mar 07
3
rosh patch V2
Here is a second version of my patch from last night.
It uses the provided ctype function isspace and does the same readdir().
I remove the rosh_issp() function. I admit to being a bit liberal with my
use of braces and spaces.
We all of the habit of knowing we can invent a more perfect wheel.
Let me know if you have any questions.
Keith
-------------- next part --------------
A non-text
2008 Oct 11
1
[PATCH] fstype: Fix ext4/ext4dev probing
Enhance fstype so it properly takes into account whether or not the
ext4 and/or ext4dev filesystems are present, and properly handles the
test_fs flag. The old code also has some really buggy checks --- for
example, where it compared the set of supported ro_compat features
against the incompat feature bitmask:
(sb->s_feature_incompat & __cpu_to_le32(EXT3_FEATURE_RO_COMPAT_SUPP)
I
2000 Dec 22
5
(HP-UX) scan: last line gets duplicated (PR#790)
The last line gets duplicated when a file is read like this:
a <- scan(file=filename, what="", sep="\n",
strip.white=c(TRUE), quiet=TRUE)
(This error does not occur on Linux, the only other platform I
tested.)
Version:
platform = hppa2.0-hp-hpux10.20
arch = hppa2.0
os = hpux10.20
system = hppa2.0, hpux10.20
Actually, all binaries are
2006 Jun 04
0
[LLVMdev] "pure" functions"
On Sun, 4 Jun 2006, Vladimir Prus wrote:
> say I've a LLVM module with a call instruction. The called function is
> "pure", that is it has no side-effects at all. How can I communicate this
> to LLVM, so that the function call can be removed if the return value is
> never used?
There isn't a way to do this from the source code yet. However, if this
is a standard
2003 Nov 24
1
[PATCH] fix off-by-one correction in ctypes
Me again,
Here's a patch to fix ctypes. There was an off-by-one correction that
looks like it isn't needed. Boundary conditions and single-entry items,
like isspace(), now work for me.
mh
--
Martin Hicks Wild Open Source Inc.
mort@wildopensource.com 613-266-2296
# This is a BitKeeper generated patch for the following project:
# Project Name: The kernel C library
2009 Sep 24
1
enabling more syntax-checks
The first c-set cleans up the list of excluded syntax-checks.
The second enables the sc_avoid_ctype_macros test and changes
each use of a ctype macro like isspace to c_isspace.
This makes it so such tests (often parsing-related) is locale-independent.
Otherwise, in some odd corner cases (combination of non-C locale
and perverted inputs), I suspect that libguestfs tools would mistakenly
accept
2023 Jul 21
1
tools::parseLatex() crashes on "\\verb{}"
Surprisingly this invalid latex syntax is still formatted "right" in the
html output.
On a closer look it seems like roxygen2 introduces those, when using
markdown backtick quoting, if the quoted content is not syntactic. For
instance:
#' `c(c(1)`
#' `c(c(1))`
Will convert the first line to `\verb{c(c(1)}` and the second to
`\code{c(c(1))}`.
I've opened a ticket there FYI: