D System Bug Report Form* 
                        
   (Download, edit, and email to dsystem-info@cs.rice.edu)


Date:

Name and email address: 
Organization:

Program: D System     Version: 0.6    Release: 

Report Type (1-6):
  1-Suggestion - nothing's broken; you just want to suggest an improvement.
  2-Design Error - change the specification or design approach.
  3-Coding Error - a logic error or coding typo; maybe i = 2 should be i < 2.
  4-Documentation Error - the program and the documentation don't agree.
  5-Question - how do you make the software do x?
  6-Hardware - the software's having trouble working with the hardware.

Attachments (1-3):
  1-Isolated source code (and data) that reproduce the problem
  2-Core file
  3-Other (corrected documentation)

Problem Summary (one line): 

Can you reproduce the problem? (y/n)
If yes, how to reproduce:

Can you work around the problem? (y/n)
If yes, how to workaround:

Detailed Problem Description:


Suggested fix (optional):



Internal use only.  Please do not write below this line.
--------------------------------------------------

Bug Report # (Functional Area & date.counter, e.g., C051694.3)
  C-Compiler
  D-Documentation
  DA-Distribution Assistant
  DB-Debugger
  E-Editor
  UI-User Interface
  P-Performance Analyzer

Severity (1-4):
  1-Minor - not inhibiting, tolerable
  2-Serious - need to fix eventually (incorrect behavior)
  3-Critical - need to fix in next release or send patch (work inhibiting)
  4-Fatal - system failure (crashes, aborts)

Assigned to:

Resolution Code (1-8):
  1-Fixed
  2-Can't reproduce it
  3-Would require substantial effort to fix
  4-Deferred until a later release
  5-Withdrawn by submitter
  6-Works to spec, misunderstanding
  7-Disagree with suggestion
  8-Developed workaround

Explanation of Resolution (this may go back to the user):


Resolved by:
Resolution tested by:
Resolution version:

Location/name of test case:


*Adapted from *Testing Computer Software* by Cem Kaner (ISBN 0-8306-9563-X)