Incomplete "fake exception" stacktraces

[David Holmes]

I'm investigating some JVM TI scenario test failures following a change 
I made in hotspot. The log shows:

The following fake exception stacktrace is for failure analysis.
nsk.share.Fake_Exception_for_RULE_Creation: (jvmti_tools.cpp:683) error
	at nsk_lvcomplain(nsk_tools.cpp:172)
# ERROR: jvmti_tools.cpp, 683: error
#   jvmti error: code=52, name=JVMTI_ERROR_INTERRUPT

and that is it. This stacktrace is completely useless as it doesn't show 
from where nsk_lvcomplain is called!

Does anyone know how this is supposed to work and whether there is some 
way for me to get a real stacktrace?

Thanks,
David