[erlang-questions] internal error in v3_life

[Håkan Mattsson]

There is no explicit calls to any function in the  'v3_life' module.
Its functions are only called via apply. This means that reltool may
have problems to determine that the module is used or not.

But as the default setting of module inclusion ('mod_cond' set to
'all') in reltool also includes all modules listed in the app file
there should be no problem.

I suspect that you have set 'mod_cond' to 'derived'. If that is the
case, reltool would not include the module.

/Håkan

On Wed, Jul 10, 2013 at 3:02 PM, Tuncer Ayaz <tuncer.ayaz@REDACTED> wrote:
> On Wed, Jul 10, 2013 at 1:02 PM, Yash Ganthe wrote:
>> Hi,
>>
>> I am getting the following error in my Erlang OTP application
>> running with
>>
>> Erlang R15B01 (erts-5.9.1) [source] [64-bit] [async-threads:0]
>> [kernel-poll:false]
>>
>> It is reporting an issue with a case_clause, but is not pointing out
>> the precise case clause.
>>
>> Any pointers will be greatly appreciated.
>>
>> Thanks,
>>
>> Yash
>>
>> ------
>>
>> (myapp@REDACTED)2> :none: internal error in v3_life;^M
>>
>> crash reason: {{case_clause,^M
>>                 {'EXIT',^M
>>                  {undef,^M
>>                   [{v3_life,module,^M
>
> Have you checked that the v3_life module is available?
>
> There was a similar problem in a reltool generated release. The issue
> was that the nodetool escript had a compile directive and the release
> was missing modules in lib/compile/ebin. So, the compiler was
> incomplete and unable to function. BTW, another common case where the
> Erlang compiler is needed in a release are Yaws applications.
>
> Relevant discussion(s):
> https://github.com/rebar/rebar/issues/64
> http://erlang.org/pipermail/erlang-questions/2013-April/073185.html
> http://erlang.org/pipermail/erlang-questions/2013-April/073323.html
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions