JDK-4950714 : JVMTI: tracing segfaults.
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: 5.0
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2003-11-07
  • Updated: 2004-01-21
  • Resolved: 2004-01-21
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0 b35Fixed
Related Reports
Relates :  
JDK-4958828 - JvmtiExport::post* functions can crash if multiple envs or tracing enabled
Relates :  
JDK-4905952 - jvmtiEnterTrace and jvmdiEnterTrace have large memory footprint
Description
I tried to run with jvmti tracing enabled, i.e. -XX:TraceJVMTI=ec 

and the vm fails during startup with the following stack trace:

  ---- called from signal handler with signal 11 (SIGSEGV) ------
  [11] ThreadLocalStorage::thread(), line 23 in "thread_solaris.inline.hpp"
  [12] Thread::current(), line 494 in "thread.hpp"
  [13] ResourceMark::ResourceMark(this = 0xffbfe524), line 85 in "resourceArea.hpp"
  [14] jvmtiTrace_GetVersionNumber(env = 0x32134, version_ptr = 0xfefc0874), line 11549 in "jvmtiEnterTrace.cpp"
  [15] jvmtiVersion(), line 858 in "util.c"
  [16] jvmtiMajorVersion(), line 870 in "util.c"
  [17] Agent_OnLoad(vm = 0xfee3f3cc, options = 0x2f660 "transport=dt_socket,address=8131,server=n,suspend=y", reserved = (nil)), line 175 in "debugInit.c"
  [18] Threads::create_vm_init_agents(), line 2884 in "thread.cpp"
  [19] Threads::create_vm(args = 0xffbfea44), line 2537 in "thread.cpp"
  [20] JNI_CreateJavaVM(vm = 0xffbff318, penv = 0xffbff314, args = 0xffbfea44), line 2380 in "jni.cpp"
  [21] InitializeJVM(0xffbff318, 0xffbff314, 0xffbff2ec, 0x29e88, 0xffbff2f4, 0x400), at 0x13304 
  [22] main(0xd, 0xffbff384, 0xffbff3bc, 0x29400, 0x0, 0x0), at 0x113dc
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger-beta2 FIXED IN: tiger-beta2 INTEGRATED IN: tiger-b35 tiger-beta2
14-06-2004
EVALUATION The trace wrappers for the jvmti functions that can be called during the onload phase need to be re-examined as they cannot use a ResourceMark before the TLS is created. ###@###.### 2003-11-09 ------------------------------------------------------------ A new SafeResourceMark was created and used in all tracing code that may be called be threads start. It uses a fixed space if called before threads exist. ###@###.### 2003-12-17
17-12-2003