Footprints: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
|Vendor=Hardy Software Systems | |Vendor=Hardy Software Systems | ||
|License= | |License= | ||
|Download= | |Download={{FileLink|FootprintsDemo_2-0.zip}} | ||
}} | }} | ||
Tracks I/O usage of OS/2 applications. | Tracks I/O usage of OS/2 applications. | ||
| Line 14: | Line 14: | ||
[[Category:Debuggers]] | [[Category:Debuggers]] | ||
[[Category: | [[Category:Commercial]] | ||
Revision as of 20:14, 17 December 2023
| Footprints | |
|---|---|
| Version | v2.0 Demo |
| Vendor | Hardy Software Systems |
| Author | |
| License | |
| Download | FootprintsDemo_2-0.zip |
| Website | |
Tracks I/O usage of OS/2 applications.
Footprints lets a developer capture real-time data and monitor a live process. Footprints consists of a DLL and a Presentation Manager executable. Developers use Footprints by including a header and linking to a DLL. The Dynamic Link Library contains four API calls used to implement tracing: initialize, terminate, trace, and check-trace. Using these C function calls, developers trace by assigning various data to any of the 64 trace IDs. Developers can also use the Check Trace feature to implement their own run-time debugging code.