Browse Prior Art Database

Facility for Setting JavaOS Debug Variables without System Rebuild

IP.com Disclosure Number: IPCOM000122892D
Original Publication Date: 1998-Jan-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 2 page(s) / 62K

Publishing Venue

IBM

Related People

Hilpert Jr, EJ: AUTHOR [+3]

Abstract

Disclosed is a mechanism that provides variables, for unit test and debug of a network computer system running JavaOS, which can be modified without the use of a debugger and without requirement for an edit / rebuild / reboot cycle. Early in the life of JavaOS, no system debugger is available, and all debug is performed with print statements. Adding these statements required editing the source, recompilation and relink, and network computer reboot. The disclosed mechanism simplifies the procedure and decreases the time required for iterative testing of cases involving multiple evaluations.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Facility for Setting JavaOS Debug Variables without System Rebuild

      Disclosed is a mechanism that provides variables, for unit test
and debug of a network computer system running JavaOS, which can be
modified without the use of a debugger and without requirement for an
edit / rebuild / reboot cycle.  Early in the life of JavaOS, no
system debugger is available, and all debug is performed with print
statements.  Adding these statements required editing the source,
recompilation and relink, and network computer reboot.  The disclosed
mechanism simplifies the procedure and decreases the time required
for iterative testing of cases involving multiple evaluations.

      This mechanism is comprised of a set of Java variables (jVars),
manipulation and display APIs, and exploitation routines in the
JavaOS command line interface and netShell thread.  The mechanism is
only intended to operate in the unit test and debug environments, and
not in  a fielded JavaOS system.  This is because the jVars are
global to the system and have no security checking as to the source
of any jVars variable changes.

      A Java class method takes advantage of the facility by
importing the sun.javaos.CondDebug package and referencing a jVar
array element in a case statement, method call, conditional, or other
programmatic usage.  This reference would then be built into the
class and the JavaOS system in a normal make.  The following is an
example of code to take advantage of such a feature:
  package sun.javaos;   // OR import sun.javaos.CondDebug;
    ...  switch (CondDebug.j...