Crash in orddict:fetch #1

Open
arcusfelis opened this Issue Jun 3, 2012 · 1 comment

Comments

Projects
None yet
2 participants
@arcusfelis
=ERROR REPORT==== 3-Jun-2012::22:56:13 ===
** Generic server erlubi_tracer terminating
** Last message in was {trace,<0.358.0>,call,
                              {erlang,demonitor,[#Ref<0.0.0.18519>]}}
** When Server state == {state,
                         {dict,52,16,16,8,80,48,
                          {[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],[]},
                          {{[[<0.0.0>|
                              {process, ....


** Reason for termination ==
** {function_clause,[{orddict,fetch,
                              [#Ref<0.0.0.18519>,[]],
                              [{file,"orddict.erl"},{line,72}]},
                     {erlubi_tracer,'-remove_monitor/3-fun-0-',2,
                                    [{file,"src/erlubi_tracer.erl"},
                                     {line,277}]},
                     {dict,update_bkt,4,[{file,"dict.erl"},{line,322}]},
                     {dict,update_bkt,4,[{file,"dict.erl"},{line,324}]},
                     {dict,on_bucket,3,[{file,"dict.erl"},{line,414}]},
                     {dict,update,4,[{file,"dict.erl"},{line,317}]},
                     {erlubi_tracer,remove_monitor,3,
                                    [{file,"src/erlubi_tracer.erl"},
                                     {line,275}]},
                     {erlubi_tracer,handle_info,2,
                                    [{file,"src/erlubi_tracer.erl"},
                                     {line,197}]}]}
@krestenkrab

This comment has been minimized.

Show comment Hide comment
@krestenkrab

krestenkrab Jun 4, 2012

Owner

Yes, we have an issue that ... when we initially build the process structure, we cannot create a MRef -> Pid mapping for monitors; there doesn't seem to be a way to get hold of that information (erlang:process_info doesn't give us that). So perhaps we should make it so that we only show monitors that have been created since tracing started...

Owner

krestenkrab commented Jun 4, 2012

Yes, we have an issue that ... when we initially build the process structure, we cannot create a MRef -> Pid mapping for monitors; there doesn't seem to be a way to get hold of that information (erlang:process_info doesn't give us that). So perhaps we should make it so that we only show monitors that have been created since tracing started...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment