JDK-8048008 : Jstack tests that verify stacktrace obtained with '-m' option should expect that system calls may not be shown
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc
  • Affected Version: 6,6u71,7,8,9
  • Priority: P3
  • Status: Closed
  • Resolution: Won't Fix
  • OS: generic
  • CPU: generic
  • Submitted: 2014-06-24
  • Updated: 2016-12-19
  • Resolved: 2016-06-15
Related Reports
Relates :  
Relates :  
Description
tmtools tests on jstack fail during verification of stacktrace obtained with '-m' options, because sometime system calls may not be shown and stacktrace contains entries like '0xb7f55402 ???????? '.

According to Dmitry's comments in JDK-8019174, there is no straightforward way to print exact function name's, to affected tests have to be updated to deal with such stacktraces.
Comments
Mixed stack trace is not supported by jstack since JDK-8155091. Please open the separate CR against jhsdb if the issue appears again.
15-06-2016

RULE tmtools/jstack/ownablesynchronizers-lm/emptyos_live Exception nsk.share.TestFailure: Jstack output does not contain debuggee stack trace RULE tmtools/jstack/ownablesynchronizers-lm/read_reentrantreadwritelock_live Exception nsk.share.TestFailure: Jstack output does not contain debuggee stack trace RULE tmtools/jstack/ownablesynchronizers-lm/reentrantlock_live Exception nsk.share.TestFailure: Jstack output does not contain debuggee stack trace RULE tmtools/jstack/ownablesynchronizers-lm/write_reentrantreadwritelock_live Exception nsk.share.TestFailure: Jstack output does not contain debuggee stack trace RULE tmtools/jstack/stacktrace-m/mixed_stack_jnj_live Exception nsk.share.TestFailure: Cannot find golden stack in jstack output
14-08-2014