How to access TemplateInterpreter::_active_table via SA in non-debug build?

Andrew Dinn adinn at
Fri Jul 27 12:25:54 UTC 2018

On 27/07/18 12:00, David Griffiths wrote:
> Appears that on Linux I can obtain the mangled form of the name:
> _ZN19TemplateInterpreter13_active_tableE. Not sure how reliable this is
> though?
I'm surprised that gdb doesn't already know how to unmangle the above
symbol if has found it for you. After all it knows all about which
compiler was used to build the binary so it ought to know how name
mangling and demangling works. Perhaps this indicates something odd in
the way your binary was built?

Anyway, in case it helps, the Red Hat OpenJDK release packages always
come accompanied with a debuginfo package that provides symbol table
information for the product code and data (in so far as such info exists
when you -O3 optimize code). I relied on that to enable my gdb stack
unwinder to unwind java frames on a product build. It provided enough
info to allow me to trawl through code cache, method and frame data. So,
if you are running on RHEL or Fedora you may find that installing the
debuginfo package(s) provides gdb with the info it needs to locate the
interpreter active table.


Andrew Dinn

More information about the hotspot-dev mailing list