Problem Report Email Body

Here is the Problem Report form:

>Submitter-Id:  <primary contact's *simplest* E-mail address (one line)>
>Originator:    <originator's name .  .  .  .  .  .  .  .  . (one line)>
>Organization:
 <originator's E-mail signature block .  .  .  .  .  . (multiple lines)>
>Confidential:  <[ no | yes ]   .  .  .  .  .  .  .  .  .  . (one line)>
>Synopsis:      <synopsis of the problem .  .  .  .  .  .  . (one line)>
>Severity:      <[ non-critical | serious | critical ]  .  . (one line)>
>Priority:      <[ low | medium | high ] .  .  .  .  .  .  . (one line)>
>Category:      totalview
>Class:         <[ sw-bug | doc-bug | change-request | support ] (1 ln)>
>Release:       5.0.0-1
>Environment:
 
 System:     <`uname -a` output .  .  .  .  .  .  .  .  .  .  .  .  .  >
 Platform:   <machine make&model, processor, etc. .  .  .  .  .  .  .  >
 OS:         <OS version and patch level .  .  .  .  .  .  .  .  .  .  >
 ToolChain:  <compiler version, linker version, etc. .  .  .  .  .  .  >
 Libraries:  <versions of parallel runtimes or standard libraries   .  >
 
 <other environmental factors you think are relevant . (multiple lines)>
 See also index.txt.
 
>Description:
 
 <precise description of the problem  .  .  .  .  .  . (multiple lines)>
 See README.TXT.
 
>How-To-Repeat:
 
 <step-by-step: how to reproduce the problem   .  .  . (multiple lines)>
 See repro.txt.
 
>Fix:
 
 <how to correct or work around the problem, if known  (multiple lines)>
 
>Unformatted:
<misc. comments, forwarded E-mail, encoded repro  .  . (multiple lines)>
 
`ls -l repro.tar.Z`  or  `cat repro.tar.Z.uu`
 
<End of problem report E-mail body.>