SLAC PEP-II
BABAR
SLAC<->RAL
Babar logo
HEPIC E,S & H Databases PDG HEP preprints
Organization Detector Computing Physics Documentation
Personnel Glossary Sitemap Search Hypernews
Unwrap page!
Comp. Search
Who's who?
Meetings
FAQ Homepage
Archive
Environment
Administration
New User Info.
Web Info/Tools
Monitoring
Training
Tools & Utils
Programming
C++ Standard
SRT, AFS, CVS
QA and QC
Remedy
Histogramming
Operations
PromptReco
Simulation Production
Online SW
Dataflow
Detector Control
Evt Processing
Run Control
Calibration
Databases
Offline
Workbook
Coding Standards
Simulation
Reconstruction
Prompt Reco.
BaBar Grid
Data Distribution
Beta & BetaTools
Kanga & Root
Analysis Tools
RooFit Toolkit
Data Management
Data Quality
Event display
Event Browser
Code releases
Databases
Check this page for HTML 4.01 Transitional compliance with the
W3C Validator
(More checks...)

FAQ Answerpage


QUESTION:
Beta in release X.Y.Z crashed. Is this a potential "bug" (or is there a fix)?

ANSWER:
(This is not a direct answer, but this is a recommended path to get results)
  1. First, look in Remedy for "recent reports" to see if anything resembles your problem. In particular, look for reports existing after the release became available.
  2. If you know which package contains the crash, do a search with that package name to get a list of all Remedy reports (not just recent or open reports) related to that package.
  3. Then, look in the Preliminary Bugs HyperNews Group for something that sounds similar.
  4. Finally, if you find nothing, (assuming you've looked through earlier Rememdy reports by now) enter the following details into a report in Remedy:
    (If you are uncertain that it is really a bug and belongs in Remedy, then put a note into Prelim bugs HN.)

    Include as much of the following information as possible:
               
          Machine type and name
          Release
          What you are running
          what you have checked out (statusrel command output)
          what command and .tcl scripts are in use
          What input data is in use
          crash description
          debugger traceback
    
    Yes, that's a lot of stuff! However, at some point, someone will ask for this information. Providing this information at the onset will help to speed up the process and saves a lot of time for the people who help you.

    (Last updated 7/17/98)

    [ SLAC Homepage]  [Search] [FAQ Homepage]
    If you have a FAQ (with or WITHOUT an answer), use our prototype submission form.
    If you have comments or suggestions, email me at sison@slac.stanford.edu