unknown_catch_try_state under R10B-2

Björn Bylander bjorn@REDACTED
Tue Dec 28 10:58:03 CET 2004


I don't get the error using R10B-1a under Windows.

On 2004-12-27 23:45, Håkan Stenholm wrote:
> I do NOT get any compile errors, compiling the code below. I use R10B-1 
> on MacOS X (10.3.6), so perhaps it's a R10B-2 or Windows relate error ?
> 
> On 27 dec 2004, at 23.05, Björn Bylander wrote:
> 
>>
>> I've reduced the incorrect code to this:
>>
>> -module(foomod).
>> -export([handle_info/2]).
>> -record(state, { foo = undefined }).
>>
>> handle_info({_}, State) ->
>>   foo(),
>>   State#state{foo = bar},
>>   case ok of
>>   _ ->
>>     case catch foo() of
>>     ok ->
>>       {stop, State}
>>     end
>>   end;
>>
>> handle_info(_, State) ->
>>   (catch begin
>>     foo(),
>>     State#state{foo = bar}
>>   end),
>>   case ok of
>>   _ ->
>>     case catch foo() of
>>     ok ->
>>       {stop, State}
>>     end
>>   end.
>>
>> foo() -> ok.
>>
>> On 2004-12-27 21:48, Björn Bylander wrote:
>>
>>> I get the following output from make:all([load]) with R10B-2 under 
>>> Windows. The module (admctrl_srv.erl) compiles fine under R9C-2, 
>>> R9C-1 and R9C-0. I haven't tried other R10 releases.
>>> Recompile: admctrl_srv
>>> admctrl_srv: function handle_info/2+2032:
>>>   Internal consistency check failed - please report this bug.
>>>   Instruction: {'%live',1}
>>>   Error:       unknown_catch_try_state:
>>> ./Admctrl_srv.erl:103: Warning: variable 'From' is unused
>>> Apart from the obvious bug I find the first warning message odd in 
>>> that the 'a' in the module file name is an upper case 'a' and not a 
>>> lower case 'a' as it actually is and also is written in the warnings 
>>> following it...
>>> Is there any info in the error message about the row on which this 
>>> occurs or do I have to try locate the row some other way?
>>> /Björn Bylander
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bjorn.vcf
Type: text/x-vcard
Size: 276 bytes
Desc: not available
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20041228/2a334553/attachment.vcf>


More information about the erlang-questions mailing list