R help - Aug 2018 - Mysterious seg fault --- SOLVED

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 <r.turner at auckland.ac.nz>
wrote:
> 
> 
> On 13/08/18 20:45, Henrik Bengtsson wrote:
> 
>> On Mon, Aug 13, 2018 at 3:51 AM Rolf Turner <r.turner at
auckland.ac.nz> 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 .Fortran() I had a line
>>> 
>>>      nphi=as.integer(nphi),
>>> 
>>> but "nphi" was nowhere defined (!!!) in the R code.  The
name "nphi"
>>> appeared as an argument in the Fortran subroutine in question, but
was
>>> nowhere actually *used*!!!
>> Didn't R CMD check pick this up, that is, didn't it report that
'nphi'
>> is a "global" variable?
> 
> No it didn't.  The name only appears in the call to .Fortran().  I
think if it appeared in a call to an ordinary garden-variety R function then a
warning would have been issued.
> 
> Such a lapse would be hard for R CMD check to pick up.  E.g
> 
>   nphi=integer(1),
> 
> would be OK in a call to .Fortran (which would allow a value of nphi,
calculated within the called subroutine, to be *returned*) whereas
> 
>   nphi=as.integer(nphi),
> 
> causes trouble when nphi has never been defined (as I found out after a
great expenditure of time and torn-out hair).  In the former instance it
doesn't matter an FTCF whether nphi has been defined or not.
> 
> cheers,
> 
> Rolf
> 
> -- 
> Technical Editor ANZJS
> Department of Statistics
> University of Auckland
> Phone: +64-9-373-7599 ext. 88276
> 
> ______________________________________________
> R-help at r-project.org mailing list -- To UNSUBSCRIBE and more, see
> https://stat.ethz.ch/mailman/listinfo/r-help
> PLEASE do read the posting guide
http://www.R-project.org/posting-guide.html
> and provide commented, minimal, self-contained, reproducible code.
-- 
Peter Dalgaard, Professor,
Center for Statistics, Copenhagen Business School
Solbjerg Plads 3, 2000 Frederiksberg, Denmark
Phone: (+45)38153501
Office: A 4.23
Email: pd.mes at cbs.dk  Priv: PDalgd at gmail.com

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 possible.  Way beyond my level of comprehension but.

cheers,

Rolf

-- 
Technical Editor ANZJS
Department of Statistics
University of Auckland
Phone: +64-9-373-7599 ext. 88276

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: object 'nphi' not found

so I think we need an alternative hypothesis about what went wrong for you... 

If nphi was NULL from the outset, that could explain things.

-pd

> On 14 Aug 2018, at 01:16 , Rolf Turner <r.turner at auckland.ac.nz>
wrote:
> 
> 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
possible.  Way beyond my level of comprehension but.
> 
> cheers,
> 
> Rolf
> 
> -- 
> Technical Editor ANZJS
> Department of Statistics
> University of Auckland
> Phone: +64-9-373-7599 ext. 88276
-- 
Peter Dalgaard, Professor,
Center for Statistics, Copenhagen Business School
Solbjerg Plads 3, 2000 Frederiksberg, Denmark
Phone: (+45)38153501
Office: A 4.23
Email: pd.mes at cbs.dk  Priv: PDalgd at gmail.com