Patent Application
20080155347
The present invention relates generally to error detection/correction and fault detection/recovery in computerized systems, and more particularly to means or steps for recording output from the system under test or diagnosis.
Dedicated debugging interfaces are widely used to log status and error messages from a running computerized system. Unfortunately, these interfaces often require specialized hardware that is expensive and difficult to use. Sometimes the debugging interface, such as the Joint Test Action Group (JTAG) interface, for example, may require its own dedicated hardware bus which has to be physically exposed outside of the system being tested or debugged. This is frequently awkward and, especially on production systems, these specialized interfaces may not be made accessible because of cost, mechanical, or security considerations.
One common solution to this problem is to log messages using another general-purpose communications bus or storage mechanism that exists on the system under test. For example, messages may be logged to a general-purpose bus (e.g., a serial port) or to a file stored on a hard disk drive. One disadvantage of this, however, is that the debugging messages may interfere with the normal purpose of the bus or storage device, especially if those mechanisms are also under test. For example, storing the debug messages in a file on a storage device might change the behavior of the native file system, by filling up storage space or by adding directory and file entries. If the file system is the module which is being tested, this might then interfere with reproduction of defects or change performance metrics. It might also be difficult to access the logged messages while the bus or storage device is under test. Instead, the messages may have to be read out after testing has been completed, thus losing any real-time logging capability.
Accordingly, what is needed is a less invasive and more real-time mechanism for exporting debugging messages on computerized systems that maintain externally accessible file system structures.
Accordingly, it is an object of the present invention to provide a debug logging mechanism for computerized systems that is embodied as a file system directory for external access.
Briefly, one preferred embodiment of the present invention is a system for handling debug log messages in a computerized device under test having a filesystem and a communications link. A virtual debug folder provides one or more virtual folders to store the debug log messages as synthesized filenames. The virtual folders are then viewable via the communications link as if they are actual folders of the filesystem and the synthesized filenames are viewable via the communications link as if they are actual filenames of the filesystem.
Briefly, another preferred embodiment of the present invention is a method for making debug log messages in a computerized device under test having a filesystem viewable via a communications link. One or more virtual folders are provide, wherein the virtual folders are viewable via the communications link as if they are actual folders of the filesystem. Synthesized filenames are then created in the virtual folders based on the debug log messages, and they also are viewable via the communications link as if actual filenames of the filesystem.
These and other objects and advantages of the present invention will become clear to those skilled in the art in view of the description of the best presently known mode of carrying out the invention and the industrial applicability of the preferred embodiment as described herein and as illustrated in the figures of the drawings.
The purposes and advantages of the present invention will be apparent from the following detailed description in conjunction with the appended figures of drawings in which:
In the various figures of the drawings, like references are used to denote like or similar elements or steps.
A preferred embodiment of the present invention is a debug log embodied as a file system directory. As illustrated in the various drawings herein, and particularly in the view of
The underlying filesystem 16 that is the basis of the virtualization by the VDF 14 should support filenames of significant length and richness in order to expose the debug log messages 22 efficiently. Also, some escaping of the debug log messages 22 may have to be done in order to accommodate restrictions placed on name composition by the filesystem 16. For example, many filesystems today reserve some characters for special uses. If such characters are valid in the debug log messages 22, they can be translated to other characters or character strings that are valid. For instance, the reserved colon character (“:”) can be replaced with “&58;” where the number 58 is the decimal value for the colon character in ASCII (i.e., this can be done much like some special characters are represented in HTML).
Although a VDF 14 can be created using any communications channel, one simple approach is to extend an existing remote file system protocol. Some example protocols for this include the Network Filesystem (NFS) or Server Message Block (SMB) networked file system protocols, or the Picture Transport Protocol (PTP) USB object storage and transfer protocol. Since protocols like these already have to virtualize a native filesystem for presentation to a remote file system client, creating additional virtual file system resources is straightforward and is likely to be non-intrusive and to minimally add protocol overhead.
Since the message order of the debug log messages 22 should be preserved in the virtual folder 36 (or folders) of the VDF 14, even when the host 18 applies a filename sort, the VDF 14 may prepend a log line number or other serialized value that will cause the sorted synthesized filenames 34 to be presented in debug log order. The date and time fields of the synthesized filenames 34 can also be mapped to debug log order, or to timing information contained within the debug log, so that timing information for each debug log message 22 may be determined by looking at the date and time fields of the synthesized filenames 34.
Given the amount of debugging log information that can be generated by a DUT 12, the debug log messages 22 can be distributed into many virtual folders 36 in the VDF 14, instead of just a single one. This grouping can accommodate filesystems 16 that perform poorly with large numbers of files in a single folder, and may also be used to group the debug log messages 22 by message type, time, or another attribute.
The VDF 14 can easily also implement a mechanism whereby the host 18 can completely or partially clear the device debug log, by deleting the virtual folder 36 (or folders) in the VDF 14, or by deleting individual synthesized filenames 34 (single debug messages) using normal operations of the filesystem 16.
Given the sensitivity surrounding debug messages, especially on DUTs 12 that may be shipped computerized systems already in customer hands, the VDF 14 may optionally implement encryption of the debug log messages 22, again using a display/output format that is suitable for the underlying filesystem 16. Also, a mechanism controlled by the host 18 for enabling the VDF 14 can be employed so that debug logging messages are not visible unless the host 18 has first triggered the VDF 14 by performing an enable sequence of operations in the filesystem 16. For example, by creating a virtual folder 36 named “DEBUG” in the target DUT 12. Alternately, particular attributes supported by the underlying filesystem 16, such as “HIDDEN” or “SYSTEM,” for instance, can be applied so that only sophisticated users could access the debug log messages 22.
While various embodiments have been described above, it should be understood that they have been presented by way of example only, and that the breadth and scope of the invention should not be limited by any of the above described exemplary embodiments, but should instead be defined only in accordance with the following claims and their equivalents.
