[erlang-questions] What does this mean?

Valentin Micic <>
Mon Oct 23 16:32:49 CEST 2006


Natural question would be, I guess -- how do these tables got corrupted in a 
first place ;-).
V.
----- Original Message ----- 
From: "Rudolph van Graan" <>
To: "Valentin Micic" <>
Cc: "Erlang List" <>
Sent: Monday, October 23, 2006 4:16 PM
Subject: Re: [erlang-questions] What does this mean?


> Hey,
>
> The only code in the system that has a binary_to_term:
>
> ./mnesia/src/mnesia_lib.erl:    Core = binary_to_term(Bin),
> ./mnesia/src/mnesia_tm.erl:    Commit = binary_to_term(Bin),
> ./mnesia/src/mnesia_tm.erl:    do_abort(Tid, binary_to_term(Bin));
> ./mnesia/src/mnesia_tm.erl:    do_commit(Tid, binary_to_term(Bin));
> ./mnesia/src/mnesia_tm.erl:    do_commit(Tid, binary_to_term(Bin), 
> DumperMode);
> ./mnesia/src/mnesia_tm.erl:         binary(Commit0) -> binary_to_term 
> (Commit0);
> ./mnesia/src/mnesia_tm.erl:                 binary(Commit0) -> 
> binary_to_term(Commit0);
>
> That is why I wondered about mnesia and corrupt tables.
>
> Rudolph van Graan
>
> Software Architect
> Pattern Matched Technologies
>
> E-Mail:  
> Tel:     086 1000 700 (SA Only)
> Mobile:  +27 83 390 7767
> Fax:     +27 12 665 9566
> Web:     www.patternmatched.com
>
>
> On Oct 23, 2006, at 4:06 PM, Valentin Micic wrote:
>
>> Similar things were happening (more violently though -- core dump) 
>> before, when attempting to use binary_to_term for selected binary 
>> values.
>> Could it be that you have a bunch of binary data that you're trying  to 
>> convert back to erlang terms?
>>
>> V.
>>
>> ----- Original Message ----- From: "Mikael Pettersson"  <>
>> To: "Rudolph van Graan" <>
>> Cc: "Erlang List" <>
>> Sent: Monday, October 23, 2006 3:42 PM
>> Subject: Re: [erlang-questions] What does this mean?
>>
>>
>>> Rudolph van Graan writes:
>>> > Hey again,
>>> >
>>> > Is it possible for a corrupt mnesia table to trigger this error?
>>> >
>>> > Rudolph van Graan
>>> >
>>> > Software Architect
>>> > Pattern Matched Technologies
>>> >
>>> > E-Mail:  
>>> > Tel:     086 1000 700 (SA Only)
>>> > Mobile:  +27 83 390 7767
>>> > Fax:     +27 12 665 9566
>>> > Web:     www.patternmatched.com
>>> >
>>> >
>>> > On Oct 23, 2006, at 2:24 PM, Mikael Pettersson wrote:
>>> >
>>> > > Rudolph van Graan writes:
>>> > >> 1> TYPE ASSERTION FAILED, file beam/erl_term.c, line 105:
>>> > >> tag_val_def: 0x18
>>> > >
>>> > > It means that you should immediately prepare a bug report
>>> > > containing at least the version of OTP you're using, the
>>> > > environment in which it is being run (OS version), the
>>> > > tools used to compile it (compiler and version), and a
>>> > > recipe for reproducing the error.
>>> > >
>>> > > This message is potentially serious and must be investigated.
>>>
>>> The message can be triggered by two different kinds of error:
>>> 1. A logic error in the BEAM runtime system causing it to access
>>>   data using type-incorrect accessors.
>>> 2. Corrupt data that no longer matches the runtime system's
>>>   expectations.
>>>
>>> I don't know enough about mnesia to comment on whether it
>>> could be the culprit here.
>>>
>>> /Mikael
>>> _______________________________________________
>>> erlang-questions mailing list
>>> 
>>> http://www.erlang.org/mailman/listinfo/erlang-questions
>>
>>
>
> 




More information about the erlang-questions mailing list