Excelsior Forums: Diagnostics of unrecoverable errors - Excelsior Forums

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Diagnostics of unrecoverable errors

#1 User is offline   zztop 

  • Advanced Member
  • Group: Moderators
  • Posts: 331
  • Joined: 09-February 05

Posted 20 February 2009 - 08:19 AM

Unrecoverable errors are those preventing the program from further execution, that is, the errors (crashes) which cannot be handled.

A known example is access violation that occurs when reading/writing memory at an address to which no memory page was mapped or transferring control to such a region. If a JET-compiled application runs into the problem, the Runtime prints TRAP#3 message and execution abnormally terminates.

Of course, it should never happen in a pure Java application but, unfortunately, it may happen due to:

  • bugs in the native method libraries used by the application
  • JNI misuses (correct usage of JNI is tricky for inexperienced programmers)
  • operating system malfunction (yes, we found a few examples when debugging)
  • bugs in the JET Optimizer or Runtime (despite it?s a rare case for the matured versions released last years, we must be honest with you  8) )


Often, the errors are volatile, that is, hardly reproducible. I recall a support case when an Excelsior JET customer received reports about an unrecoverable error from his customers but he could not reproduce it in his test environment. Of course, he was not able to provide Excelsior Support with a sample on which the problem appeared. After many trilas we finally managed to find the root cause but it was double tough.

To address the problem, we scheduled implementing a special diagnostic facility in Excelsior JET 6.5. If an unrecoverable error occurs, the JET Runtime collects various information about the application state, logs it into a file, and prints the error message referencing that file. We believe this feature will enable us to reveal the root cause of the errors faster and easier and help our customers.

The diagnostic logging has been already implemented and is available in Excelsior JET 6.5 beta 4.


#2 User is offline   pdot 

  • Newbie
  • Pip
  • Group: Members
  • Posts: 6
  • Joined: 09-January 06

Posted 10 March 2009 - 07:18 AM

Fantastic feature, we've been using it in our local test environments to diagnose a weird issue with a third party library.  Any information about when 6.5 might be released ?

EDIT: Never mind found a reference in another thread, "We are planning to release JET 6.5 in the middle of March 2009".
0

#3 User is offline   zztop 

  • Advanced Member
  • Group: Moderators
  • Posts: 331
  • Joined: 09-February 05

Posted 10 March 2009 - 01:50 PM

Quote

EDIT: Never mind found a reference in another thread, "We are planning to release JET 6.5 in the middle of March 2009".


Exact dates may vary  8)

May 2009 would be a more realistic estimate

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users