Strange stack-traces in crash reports

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Strange stack-traces in crash reports

Alexey Lebedeff-3
Hi folks,

In sasl logs I'm observing some stack-traces that I can't explain, on Erlang 18.1 + actively using HiPE compilation. Looks like those are stack-traces of 2 different processes somehow merged together.

Here are some examples:

** {function_clause,[{gb_trees,delete_1,2,[]},
                     {gb_trees,delete,2,[]},
                     {mirrored_supervisor,init,1,[]},
                     {gen_server2,handle_msg,2,[]},
                     {mirrored_supervisor,init,1,[]}]}
But there is no way it can call:
- itself recursively
- gen_server2:handle_msg/2
- gb_trees:delete/1


** {function_clause,[{rabbit_channel,handle_info,2,[]},
                     {gen_server2,handle_msg,2,[]},
                     {ssl_config,module_info,1,[]}]}

And according to this trace, `ssl_config:module_info/1` somehow started process of message handling in generic server, which doesn't make any sense. And this `module_info` happens with a lot of different modules, both built-in and application specific.


Is this something known? Can it be related to HiPE? I was not able to find anything related to stacktraces in release notes of every 18 and 19 release.


Best,
Alexey

_______________________________________________
erlang-bugs mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-bugs
Loading...