Zitat von David (Wed, 12 Sep 2012 01:38:50 -0400)
I am trying to do a classic
R -d valgrind --vanilla < mypkg-Ex.R
as described in
http://cs.swan.ac.uk/~csoliver/ok-sat-library/internet_html/doc/doc/R/2.9.1/doc/manual/R-exts.html#Using-valgrind
The problem is valgrind crashes imediately.
[.
> Martin Morgan
> on Tue, 25 Sep 2012 05:34:12 -0700 writes:
> On 09/25/2012 05:26 AM, Martin Maechler wrote:
>>
>>> Seemed like a good idea at the time,
>>
>> I'm curious. Why is it (setting max.print much too
>> large) a good idea?
> I usually set it
On 09/25/2012 05:26 AM, Martin Maechler wrote:
Seemed like a good idea at the time,
I'm curious. Why is it (setting max.print much too large)
a good idea?
I usually set it considerably smaller (50) than default to conserve
screen real estate, but then occasionally need to see more than my
> Seemed like a good idea at the time,
I'm curious. Why is it (setting max.print much too large)
a good idea?
> but
> > options(max.print = .Machine$integer.max)
> > 1:10
> [1]
> Program received signal SIGSEGV, Segmentation fault.
> because of an integer overflow at src/main/p
On Sep 25, 2012, at 04:45 , Thomas Lumley wrote:
> Is there some reason why
>
>> (1:2)+(1:3)
> [1] 2 4 4
> Warning message:
> In (1:2) + (1:3) :
> longer object length is not a multiple of shorter object length
>
> can't be made into an error? I realise it was there in S-PLUS, but
> since it
On 25/09/2012 08:12, Prof Brian Ripley wrote:
On 25/09/2012 03:45, Thomas Lumley wrote:
Is there some reason why
(1:2)+(1:3)
[1] 2 4 4
Warning message:
In (1:2) + (1:3) :
longer object length is not a multiple of shorter object length
can't be made into an error? I realise it was there i
On 25/09/2012 03:45, Thomas Lumley wrote:
Is there some reason why
(1:2)+(1:3)
[1] 2 4 4
Warning message:
In (1:2) + (1:3) :
longer object length is not a multiple of shorter object length
can't be made into an error? I realise it was there in S-PLUS, but
since it produces a warning there
