[erlang-questions] process_info/2 returning badarg with message_que_len

Anthony Ramine <>
Tue Apr 23 11:38:59 CEST 2013


Hello Bryan,

This will be fixed in R16B01, a patch has been submitted by Andrew Tunnell-Jones.

Regards,

-- 
Anthony Ramine

Le 23 avr. 2013 à 00:40, Bryan Hughes a écrit :

> Thanks Bob!
> 
> It is a typo in the docs.  
> 
> http://erlang.org/doc/man/erlang.html#process_info-2
> 
> process_info_item() = backtrace
>                     | binary
>                     | catchlevel
>                     | current_function
>                     | current_location
>                     | current_stacktrace
>                     | dictionary
>                     | error_handler
>                     | garbage_collection
>                     | group_leader
>                     | heap_size
>                     | initial_call
>                     | links
>                     | last_calls
>                     | memory
>                     | message_que_len       <======== TYPO
>                     | messages
>                     | min_heap_size
>                     | min_bin_vheap_size
>                     | monitored_by
>                     | monitors
>                     | priority
>                     | reductions
>                     | registered_name
>                     | sequential_trace_token
>                     | stack_size
>                     | status
>                     | suspending
>                     | total_heap_size
>                     | trace
>                     | trap_exit
> 
> 
> Cheers,
> B
> 
> On 4/22/13 3:38 PM, Bob Ippolito wrote:
>> Is that a typo in the docs? Should be message_queue_len. 
>> 
>> On Monday, April 22, 2013, Bryan Hughes wrote:
>> Howdy,
>> 
>> I am having some weirdness.  Running on the latest build of R16B (erts-5.10.1).  Per the documentation (http://erlang.org/doc/man/erlang.html#process_info-2),
>> when I call it:
>> 
>> Info = erlang:process_info(self(), [memory, heap_size, message_que_len]),
>> 
>> I get the following error:
>> 
>> * Reason for termination ==
>> ** {badarg,[{erlang,process_info,
>>                     [<0.127.0>,[memory,heap_size,message_que_len]],
>>                     []},
>> 
>> When I call it without message_que_len, or instead use messages:
>> 
>> Info = erlang:process_info(self(), [memory, heap_size, messages]),
>> 
>> Life is good.  According to the docs, message_que_len is a valid process_info_item().  Is the documentation wrong, or am I doing something wrong?
>> 
>> Note that this also happens in the shell.
>> 
>> Thanks again!
>> 
>> Cheers,
>> Bryan
>> 
>> -- 
>> Bryan Hughes
>> Go Factory
>> http://www.go-factory.net
>> 
>> "Art is never finished, only abandoned. - Leonardo da Vinci"
>> 
> 
> 
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions



More information about the erlang-questions mailing list