BUGREPORT 2.9 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879
  1. [Created from Graphlet/bugreport.html]
  2. Suggestions for Bug Reports
  3. _________________________________________________________________
  4. Bug report address
  5. Send bug reports to graphlet@fmi.uni-passau.de, or send them to the
  6. responsible person on the Graphlet team if you know her/him.
  7. _________________________________________________________________
  8. What you should send us
  9. Description
  10. Give a description of the bug. If possible, tell us how we can
  11. reproduce the bug. "Graphlet sometimes chrashes" without any
  12. further information will not help us much.
  13. Operating System
  14. We need your operating system, as some bugs occur only with
  15. specific operating systems. Please Include the version number
  16. of the operating system if possible.
  17. Graphlet Version
  18. Please include the version number of Graphlet. Without this
  19. information, we may not be able to reproduce the bug correctly.
  20. Tcl/Tk and LEDA versions
  21. If possible, include the version numbers of Tcl/Tk and LEDA.
  22. You can get the version number of Tcl from graphscript:
  23. prompt> graphscript
  24. & info tclversion
  25. 7.5
  26. Control-D
  27. Since the version numbers of Tcl and Tk are tightly coupled, the Tcl
  28. version is sufficent. Question to the reader: is there a easy
  29. way to find the version number of LEDA ?
  30. _________________________________________________________________
  31. For Installation Problems ...
  32. Include the output of make
  33. It is often a good idea to include the output of make.
  34. Include the configuration files
  35. Send us the file lib/graphlet/config/config. If you modified
  36. other files in the directory lib/graphlet/config, please
  37. include them.
  38. Version numbers
  39. As always, is useful to include the version number of the
  40. program that failed. E.g. if make reports a syntax error, it
  41. might be helpful for us to know the version number of make.
  42. _________________________________________________________________
  43. For Runtime Errors ...
  44. Tcl Runtime Errors
  45. If graphlet reports a tcl error, please return the full tcl
  46. error message. Tcl's error messages are a complete stack trace
  47. and give very precise idea what goes wrong.
  48. Crashes
  49. If graphlet crashes, try to give a precise description. If you
  50. have a specific graph which causes a crash, send it. If you
  51. have a stack trace from a debugger, send it.
  52. _________________________________________________________________
  53. Thanks
  54. I know we are asking for a lot, but the more information we get, the
  55. better we will be able to track down your problem.
  56. _________________________________________________________________