JDK-4638005 : For most cases errorid string is not specific enough or complete/accurate
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.4.1
  • Priority: P5
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_8
  • CPU: sparc
  • Submitted: 2002-02-14
  • Updated: 2002-03-12
  • Resolved: 2002-03-12
Related Reports
Duplicate :  
What we would like is a way to dump the stack when an error occurs and dump this data to the hs_error.log file.  This will help give us a better idea as to a starting point for debugging a customers problem. Complete stack dump that is.
This is ok if we can't do this for all cases but at least this is a starting point.

EVALUATION Karen, this is the bug we discussed in your office that you asked me to file. Thanks Gary ###@###.### 2002-02-14 ###@###.### 2002-02-26 In many error cases we will not be able to dump all stacks since that requires getting to a safepoint - and since this is to handle an internal vm problem, that is usually not doable and attempting to do so would simply cause a further problem which would muddle the error report. There are probably a set of cases where we could fairly safely dump the current thread's stack. It is not clear what information we want on the screen in product mode, and it is not clear for which errors the stack would show the most useful information. There are error cases where showing a small set of values (such as the field that failed the test) might be more useful. This needs more investigation. Not committing to Hopper at this time.