Text bugreport template

Jens Skripczynski jens.skripczynski at igd.fhg.de
Tue Apr 11 23:22:09 EST 2000


Hi,

I think by giving people some bugreport template it is possible to
improve the quality of the bugreports and so save time at the searching
for the actual error.

I've attached two fieles. One containing general guidlines for the report 
and a second file as an empty template file. The will contain lots of erros,
and might miss some necassary information. I would like you to look over the
files, and give feed-back for improvements.


Ciao

Jens Skripczynski
-- 
E-Mail: skripi at igd.fhg.de

Computers are like airconditioners: They stop working 
properly if you open windows.
-------------- next part --------------
 G E N E R A L                  |
--------------------------------+

Before you send a bugreport to the list, please make sure that you
have the latest samba code. 

If you are using cvs, it is sometimes possible, that your local sourcetree 
isn't in sync with the cvstree anymore. You will have to remove all source
files and do a fresh checkout.

For a fast responce and efficient bug tracking it is mandatory, that you
answer the following questions as soon as possible, as the guys of the samba
team have a lot to do, and each minute you invest may save them hours of work
( and giving the error a higher priority).

Typing:
Things separated by a "|" symbol are an or combination. So (A|B) means you
can choose "A" or "B".
A "$WORD" Means substitute $WORD by your local conditions
`command -option` means execute the command with the options

general Information             |
--------------------------------+

OS: Please submit the Operating System you are using with Version number.
    ex: - Linux (Suse|Redhat|Mandrake) $VERSION $KERNELVERSION
        - SPARC $VERSION
        - ....
   `uname -a` typed in your shell should reveal most information. If not
   "ask your local system administrator... ;)"

Compiler: The compiler you are using. Even if samba is written Posix compient
          it may happen, that some compilers do make a difference on
          interpreting code.
     For the gcc compiler `gcc -v` reveals the version number.
     For others consult the man page. `man $COMPILER`

CVS-Branch: Contains the CVS-Branch you are Using. Valid itmes are:
            SAMBA_TNG|SAMBA_2_0_RELEASE|SAMBA_2_0|HEAD

Version/Date: Contains either the Version number of the tar-ball you got from
              the official samba ftp or http server, or if you are using cvs,
              the date _and_ time of your last update (don't forget to mention 
              the timezone).

error Type   : reproduceable | random
               Is the error type. Reproduceable errors have the highest
               priority, as they can be tracked down easier. Random errors
               are more a call for someone to go fishing in the mist.

Short Desc.   : A short description when the error occurs. Logon, accessing a
                share / printer, joining the Domain etc.

Trigger        : How to trigger the error. "If i click on the Internet Explorer
                 my Harddisk catches fire...."


special Information             |
--------------------------------+

If you catch in your log-files something like: "INTERNAL ERROR... see
Bugs.txt". Then you have to compile samba in a special debug mode:
If not continue with 4).

1) recompile with debug information :
        + cvs update
        + make distclean
        + ./configure.developer
        + make
        + make install
        + edit smb.conf: Change "debug level = 100"
        + restart all samba daemons

2) If it core dumps again with : "INTERNAL ERROR... see Bugs.txt". Else
continue with 3).
 `gdb $PROCESSNAME core`
 + type where
 + again send E-Mail as noted above with the information of gdb

3) attach the full log-files of the corresponding daemon 


4) attach you configuration files. Usually the smb.conf should suffice.


-------------- next part --------------
   G E N E R A L
  * * * * * * * *
-------------
OS          :
-------------
Compiler    :
-------------
CVS-Branch  :
-------------
Version/Date:
-------------
Error Type  :
-------------
Short Desc. :
-------------
Trigger     :
-------------

   S P E C I A L
  * * * * * * * *

-------------
GBD         :
-------------

-------------
Log-Files   :
-------------

-------------
smb.conf    :
-------------



More information about the samba-cvs mailing list