[erlang-questions] Inspecting db_hash_slot locks with lcnt

[Defnull]

Hi,

I got acquainted with Lcnt not far ago and found it a really great tool.
While digging into the performance problems with the application i noticed 
that by mistake one of the highly used ets did not have concurrency options 
turned on for writes. 
It was rather easy to find it by simply inspecting lcnt:inspect(db_tab) as 
it shows on which tables this lock appear. But what a pity I could not find 
any information on which etss
db_hash_slot appear. db_hash_slot's ids are common integers and as i 
understand there is no way to find out on wich table they arise.

Is it just a lack of functionality, or I just missed something in the 
documentation?
I can see the same picture with some others lock classes as well.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20131115/028702e2/attachment.htm>