ays please Rolf, all!
Chris
- Original Message -
> From: "Rolf Turner"
> To: "Richard M. Heiberger"
> Cc: r-help@r-project.org, "Achim Zeileis" , "peter
> dalgaard" , "Henrik
> Bengtsson"
> Sent: Wednesday, 15 August,
On 15/08/18 13:00, Richard M. Heiberger wrote:
There is no explanation other than gremlins and the malevolence that
the computer gods hold towards me.
fortune nomination.
I demur. I already have a fortune with gremlins in it attributed to me
(fortune(213)).
cheers,
Rolf
--
Technical Editor
There is no explanation other than gremlins and the malevolence that
the computer gods hold towards me.
fortune nomination.
On Tue, Aug 14, 2018 at 7:12 PM, Rolf Turner wrote:
> On 14/08/18 23:01, peter dalgaard wrote:
>>
>> Hmm,
>>
>>> .Fortran(stats:::C_setsmu, as.integer(0))
>>
>> [[1]]
>> [1
On 14/08/18 23:01, peter dalgaard wrote:
Hmm,
.Fortran(stats:::C_setsmu, as.integer(0))
[[1]]
[1] 0
.Fortran(stats:::C_setsmu, as.integer(fumble))
Error: object 'fumble' not found
.Fortran(stats:::C_setsmu, fumble=as.integer(fumble))
Error: object 'fumble' not found
.Fortran(stats:::C_se
Hmm,
> .Fortran(stats:::C_setsmu, as.integer(0))
[[1]]
[1] 0
> .Fortran(stats:::C_setsmu, as.integer(fumble))
Error: object 'fumble' not found
> .Fortran(stats:::C_setsmu, fumble=as.integer(fumble))
Error: object 'fumble' not found
> .Fortran(stats:::C_setsmu, nphi=as.integer(nphi))
Error: objec
On 13/08/18 23:39, peter dalgaard wrote:
It's odd, possibly a bug, that you don't get
Error: object 'nphi' not found
but I can't offhand see where the evaluation of args to .C/.Fortran is supposed
to take place.
If it is indeed a bug then it would be nice an it were fixed. If that
is possi
It's odd, possibly a bug, that you don't get
Error: object 'nphi' not found
but I can't offhand see where the evaluation of args to .C/.Fortran is supposed
to take place.
-pd
> On 13 Aug 2018, at 11:54 , Rolf Turner wrote:
>
>
> On 13/08/18 20:45, Henrik Bengtsson wrote:
>
>> On Mon, Aug
On 13/08/18 20:45, Henrik Bengtsson wrote:
On Mon, Aug 13, 2018 at 3:51 AM Rolf Turner wrote:
OK everybody! You can relax. :-) I managed to spot the loony. After
mucking around with valgrind, and before trying gdb, I had one more look
at my code and *finally* saw the stupid thing that I
On Mon, Aug 13, 2018 at 3:51 AM Rolf Turner wrote:
>
>
> OK everybody! You can relax. :-) I managed to spot the loony. After
> mucking around with valgrind, and before trying gdb, I had one more look
> at my code and *finally* saw the stupid thing that I had been doing.
>
> In the call to .Fort
OK everybody! You can relax. :-) I managed to spot the loony. After
mucking around with valgrind, and before trying gdb, I had one more look
at my code and *finally* saw the stupid thing that I had been doing.
In the call to .Fortran() I had a line
nphi=as.integer(nphi),
but "nphi"
On 13/08/18 12:03, Duncan Murdoch wrote:
So I did:
/usr/local/bin/valgrind R
I believe on your system R is a script, so you can't run valgrind this
way. It's just debugging bash, not R. You need to use
R -d valgrind
(though with your weird path problems, you might need a fully qualifi
On 12/08/2018 6:32 PM, Rolf Turner wrote:
On 12/08/18 17:42, Eric Berger wrote:
Hi Rolf,
When faced with such a situation I take the following approach which
often helps.
Use the same setup that caused the seg fault (you need a reproducible
problem.)
Start your R session using valgrind. e.g. i
On 12/08/18 17:42, Eric Berger wrote:
Hi Rolf,
When faced with such a situation I take the following approach which
often helps.
Use the same setup that caused the seg fault (you need a reproducible
problem.)
Start your R session using valgrind. e.g. in linux I do:
$ valgrind R
Assuming t
On 12/08/18 09:52, Göran Broström wrote:
Rolf,
have you tried to run R with a debugger, as in
$ R -d gdb
the gnu debugger?
No, I haven't. Did not know about the gnu debugger. I shall
investigate. Thanks
cheers,
Rolf
--
Technical Editor ANZJS
Department of Statistics
University of A
Hi Rolf,
When faced with such a situation I take the following approach which often
helps.
Use the same setup that caused the seg fault (you need a reproducible
problem.)
Start your R session using valgrind. e.g. in linux I do:
$ valgrind R
Assuming that a seg fault still occurs then valgrind sho
Segfaults are not always repeatable. You may have an undefined pointer that
sometime points into unreachable or unallocated memory, causing a segfault,
and sometimes may point into valid memory, without causing a segfault.
You may want to read
https://cran.r-project.org/doc/manuals/r-release/R-ext
Rolf,
have you tried to run R with a debugger, as in
$ R -d gdb
the gnu debugger?
G,
On 2018-08-11 23:12, Rolf Turner wrote:
I am getting a seg fault from a package that I am working on, and I am
totally flummoxed by it. The fault presumably arises from dynamically
loaded Fortran code, b
I am getting a seg fault from a package that I am working on, and I am
totally flummoxed by it. The fault presumably arises from dynamically
loaded Fortran code, but I'm damned if I can see where the error lies.
In an effort to diagnose the problem I created a "non-package" version
of the c
18 matches
Mail list logo
