[erlang-bugs] system_info crash

[Tony Rogvall]

On 16 jan 2013, at 19:15, Björn-Egil Dahlberg <egil@REDACTED> wrote:

> On 2013-01-14 15:00, Tony Rogvall wrote:
>> While designing a system_info debug tool I found this:
>> 
>> 
>> 7> erlang:system_info(stop_memory_trace).
>> ../include/internal/ethr_mutex.h:655: Fatal error in ethr_mutex_lock(): Invalid argument (22)
>>              Abort trap: 6
> This was one of Rickards pet project and I suspect that the memory tracer hasn't been subject to major updates since launch of smp.
> 
> It is not used, not documented, and not rigorously tested. The memory tracer should be removed IMHO (, or otherwise corrected). Rickard, opinions?
> 
I just picked all system_info I could find :-)

> I first recalled, incorrectly, that this was an opt-in configurable tracer, but I see now that isn't the case. Does this break through testcases or plain usage?
> 
Plain usage. Just call it.
(Have only tried on the config below)
/Tony

> // Björn-Egil
> 
>> 
>> Erlang R15B03 (erts-5.9.3) [source] [64-bit] [smp:2:2] [async-threads:0] [hipe] [kernel-poll:false]
>> 
>> uname -a
>> Darwin p13.local 12.2.0 Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64 x86_64
>> 
>> /Tony
>> 
>> 
>> 
>> _______________________________________________
>> erlang-bugs mailing list
>> erlang-bugs@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-bugs
>> 
>> 
> 
> _______________________________________________
> erlang-bugs mailing list
> erlang-bugs@REDACTED
> http://erlang.org/mailman/listinfo/erlang-bugs

"Installing applications can lead to corruption over time. Applications gradually write over each other's libraries, partial upgrades occur, user and system errors happen, and minute changes may be unnoticeable and difficult to fix"



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-bugs/attachments/20130116/63a34daf/attachment.htm>