[erlang-questions] Dialyzer problem on OSX 10.6 (Erlang R13B02-1)

Tamas Nagy <>
Mon Nov 9 22:42:29 CET 2009


Hi everyone,

The problem has been solved in homebrew. Aggressive optimisation for  
some reason doesn't go well with dialyzer.
The error would probably have shown its ugly head in different  
applications as well. dialyzer was only the unlucky one to reliable  
trigger it.

For all the gory details:
http://github.com/mxcl/homebrew/issues/closed/#issue/120

Tamas Nagy
Erlang Training & Consulting
http://www.erlang-consulting.com

On 9 Nov 2009, at 11:50, Tino Breddin wrote:

> Hi Tamas,
>
> Yes I used homebrew as well. That sounds strange, might it be that  
> those optimizations have a negative impact on the Erlang performance  
> on Mac OSX?
>
> Cheers,
> Tino
>
> On Nov 9, 2009, at 11:35 AM, Tamas Nagy wrote:
>
>> Hi Tino,
>>
>> Are you using homebrew?
>>
>> So far it seems that homebrew applies some c compiler magic (e.g  
>> optimizations) when building erlang which somehow borks dialyzer  
>> (strange) as compiling from source with the same ./configure  
>> options homebrew uses results in an erlang installation which works  
>> like a charm.
>>
>> Regards,
>>   Tamas
>> ----- "Tino Breddin" <> wrote:
>>
>>> Hey Tamas,
>>>
>>> Here's the output for the command run on my machine (Macbook Pro  
>>> Core
>>>
>>> Duo, running OSX 10.6.1 32-bit):
>>>
>>> dialyzer --build_plt -r /usr/local/Cellar/erlang/R13B02-1/lib/ 
>>> erlang/
>>>
>>> lib/erts-5.7.3/ebin/ /usr/local/Cellar/erlang/R13B02-1/lib/erlang/ 
>>> lib/
>>>
>>> kernel-2.13.3/ebin/ /usr/local/Cellar/erlang/R13B02-1/lib/erlang/ 
>>> lib/
>>>
>>> stdlib-1.16.3/ebin/
>>>  Creating PLT /Users/tino/.dialyzer_plt ...
>>> Unknown functions:
>>>  compile:file/2
>>>  compile:forms/2
>>>  compile:noenv_forms/2
>>>  compile:output_generated/1
>>>  crypto:des3_cbc_decrypt/5
>>>  crypto:start/0
>>> done in 46m22.52s
>>> done (passed successfully)
>>>
>>> Apparently it takes some time to complete but you'll get there.
>>>
>>> Cheers,
>>> Tino
>>>
>>> On Nov 8, 2009, at 11:35 PM, Tamas Nagy wrote:
>>>
>>>> Hi Kostis,
>>>>
>>>> This is what all I get:
>>>> $ dialyzer --build_plt -r /usr/local/Cellar/erlang/R13B02-1/lib/
>>>> erlang/lib/erts-5.7.3/ebin/ /usr/local/Cellar/erlang/R13B02-1/lib/
>>>> erlang/lib/kernel-2.13.3/ebin/
>>> /usr/local/Cellar/erlang/R13B02-1/lib/
>>>> erlang/lib/stdlib-1.16.3/ebin/
>>>> Creating PLT /Users/lestat/.dialyzer_plt ...
>>>>
>>>> I will try to rebuild erlang with disabling hipe to see if that
>>> helps.
>>>>
>>>> I am happy to run some tests/traces you would like to see the
>>>> results of to help.
>>>>
>>>> Regards,
>>>> 	Tamas
>>>>
>>>> Tamas Nagy
>>>> Erlang Training & Consulting
>>>> http://www.erlang-consulting.com
>>>>
>>>> On 8 Nov 2009, at 19:52, Kostis Sagonas wrote:
>>>>
>>>>> Tamas Nagy wrote:
>>>>>> Hi,
>>>>>> Am I the only one who cannot build a plt under OSX 10.6 in
>>>>>> R13B02-1?
>>>>>> No matter what applications I specify for the initial plt it just
>>>
>>>>>> hangs eating processing power but not producing anything.
>>>>>> Erlang was installed with homebrew, but that shouldn't matter. Or
>>>
>>>>>> maybe it does. (beam is compiled for 64 bit)
>>>>>> Here is the command I used:
>>>>>> dialyzer --build_plt -r /usr/local/Cellar/erlang/R13B02-1/lib/
>>>>>> erlang/lib/erts-5.7.3/ebin/ /usr/local/Cellar/erlang/R13B02-1/ 
>>>>>> lib/
>>>
>>>>>> erlang/lib/kernel-2.13.3/ebin/ /usr/local/Cellar/erlang/R13B02-1/
>>>
>>>>>> lib/erlang/lib/stdlib-1.16.3/ebin/
>>>>>> I gave waiting for it to finish after ~1 hour (on an old type
>>>>>> white MacBook (MacBook2,1) with 2GB of RAM).
>>>>>
>>>>> None of the dialyzer developers has access to such a machine to  
>>>>> see
>>>
>>>>> what's happening.  Perhaps somebody else in that list might want  
>>>>> to
>>>
>>>>> report whether this is reproducible or not.
>>>>>
>>>>> However, perhaps the following might help: when building the PLT,
>>>
>>>>> do you see a message:
>>>>>
>>>>> 	Compiling some key modules to native code...
>>>>>
>>>>> If so, can you disable hipe (64-bit Mac is not a platform we have
>>>
>>>>> ever tested due to no access to such a machine) to see whether  
>>>>> this
>>>
>>>>> may be the culprit?
>>>>>
>>>>> Kostis
>>>>
>>>>
>>>> ________________________________________________________________
>>>> erlang-questions mailing list. See http://www.erlang.org/faq.html
>>>> erlang-questions (at) erlang.org
>>>>
>>
>> -- 
>> Tamas Nagy
>> Erlang Training & Consulting
>> http://www.erlang-consulting.com
>>
>> ________________________________________________________________
>> erlang-questions mailing list. See http://www.erlang.org/faq.html
>> erlang-questions (at) erlang.org
>>
>



More information about the erlang-questions mailing list