Room 6351:
- Bug Finding

The return value checker we wrote checks to see if, when a function returns a value, that value is tested before being used. The need for checking the return value is intuitive in C programs since the return value of a function often may be either valid data or a special error code. The key to our checker is the ranking system used to present the output in a useful manner. Error reports are grouped by the function called. A function is ranked by how often its return value is tested before being used. This is an aggregate number generated by running the checker over all of the code in the current version of the software and tracking, for each function, the number of times the function is called and after how many of these calls the return value is used improperly. Data mined from the CVS repository describing past bug fixes also contributes to the error reports ranking. (Chadd Williams, University of Maryland)   CLOSE

Room 6376:
- DPLC (with new command line tool)
- DPOMP

Room 6370:
- Performance Analysis at Loop-level Granularity in Paradyn
- iPath: An Incremental Call-Path Profiler
- Paradyn with Multi-threaded Linux

Room 6372:
- Self-Propelled Tracing for Performance Analysis of Interactive Systems
- Analysis and Instrumentation of Stripped Binary Code
- Memory Locality

Room 6397:
- Dynamic Instrumentation on the IA-64
- Multi-platform Kerninst
- The Tool Daemon Protocol
- Data Cache tool on Itanium

Hors d'Oeurves and Soft Drinks available in Room 3331

Rooms and demonstration titles to be announced.

Participants are encouraged to eat dinner with individual team members at places of their own choosing.