From goran.brostrom at gmail.com  Thu Dec 14 23:13:31 2006
From: goran.brostrom at gmail.com (=?UTF-8?Q?G=C3=B6ran_Brostr=C3=B6m?=)
Date: Thu, 14 Dec 2006 23:13:31 +0100
Subject: [Rd] [R] Segfault in pure R code
In-Reply-To: <Pine.LNX.4.64.0612122249290.25343@gannet.stats.ox.ac.uk>
References: <148ed8180612121218pea45e0agcdb39a8b9fe9ff43@mail.gmail.com>
	<457F18AB.4020109@biostat.ku.dk>
	<148ed8180612121414x5763a5f1k4c802976fe9c85fe@mail.gmail.com>
	<148ed8180612121433n1287d12al6fdc622722d0b3ef@mail.gmail.com>
	<Pine.LNX.4.64.0612122249290.25343@gannet.stats.ox.ac.uk>
Message-ID: <148ed8180612141413o2f9a1d40l913b5cd829fc5cf2@mail.gmail.com>

On 12/13/06, Prof Brian Ripley <ripley at stats.ox.ac.uk> wrote:
> That's in the memory manager and indicates prior memory corruption.
> Please re-run under valgrind, plus gctorture(TRUE) if needed.

I did, no errors (but slow)!

> However, I would start by seeing if this occurs in a single-byte domain if
> this was in a UTF-8 domain.  Experience suggests that we have some flakier
> code in the less-used MBCS pathways.

It was/is NOT run in UTF-8.

G?ran



[Rd] [R] Segfault in pure R code
=?UTF-8?Q?G=C3=B6ran_Brostr=C3=B6m?=