From murdoch at stats.uwo.ca  Tue Sep 22 11:56:08 2009
From: murdoch at stats.uwo.ca (Duncan Murdoch)
Date: Tue, 22 Sep 2009 05:56:08 -0400
Subject: [Rd] cannot build R-devel (>= r49747)
In-Reply-To: <4AB89DE4.3000506@dbmail.com>
References: <4AB86E88.5070304@dbmail.com>
	<4AB87A07.6040605@biostat.ku.dk>	<4AB87DB6.5070507@dbmail.com>
	<4AB88D7A.7040408@dbmail.com>	<4AB897F1.3060905@biostat.ku.dk>
	<4AB89935.3040104@dbmail.com> <4AB89BDF.2090200@stats.uwo.ca>
	<4AB89DE4.3000506@dbmail.com>
Message-ID: <4AB89F38.7090605@stats.uwo.ca>

On 22/09/2009 5:50 AM, Romain Francois wrote:
> On 09/22/2009 11:41 AM, Duncan Murdoch wrote:
>> On 22/09/2009 5:30 AM, Romain Francois wrote:
>>> On 09/22/2009 11:25 AM, Peter Dalgaard wrote:
>>>> Romain Francois wrote:
>>>>
>>>>> However, this might be relevant about my setting, I have the
>>>>> "R_KEEP_PKG_SOURCE" environment variable set to "yes". And if I set it
>>>>> to "no" it builds correctly.
>>>> AHA! Yes, that makes sense
>>>>
>>>> R_KEEP_PKG_SOURCE=yes make
>>>>
>>>> breaks for me too with the unprotect_ptr message (SUSE 64bit this time).
>>>>
>>> I can now track this down to these lines in gram.(y|c)
>>>
>>> if (!isNull(ParseState.SrcFile))
>>> UNPROTECT_PTR(ParseState.SrcFile);
>>>
>>> The error occurs the first time ParseState.SrcFile is not null.
>> Thanks for this info. I can track it down now.
>>
>> Duncan Murdoch
> 
> Good. You'll probably be able to fix it much faster.
> 
> My only guess is that some extra care is needed when UNPROTECT_PTR'ing 
> environments, because if I comment this, then the same problem occurs in 
> R_FinalizeSrcRefState(SrcRefState *state) at the end of the parse.

I doubt if it has to do with the type of that object, but that object is 
treated specially, because it is a global value that can change during 
the parse.  At some point I'd guess I unprotected it twice, or failed to 
initialize it.

Duncan Murdoch



[Rd] cannot build R-devel (>= r49747)
Duncan Murdoch