From 27aef6855f1543547b8190f06fd264d1b52a558d Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Sun, 6 Apr 2003 18:42:44 +0000 Subject: Regenerate docs (This used to be commit 5a2aaa3d5b039776314067aee953921e7865dc4d) --- docs/htmldocs/bugreport.html | 99 ++++++++++++++++++++++++++++++-------------- 1 file changed, 67 insertions(+), 32 deletions(-) (limited to 'docs/htmldocs/bugreport.html') diff --git a/docs/htmldocs/bugreport.html b/docs/htmldocs/bugreport.html index 0711f00f80..2ba74f5192 100644 --- a/docs/htmldocs/bugreport.html +++ b/docs/htmldocs/bugreport.html @@ -74,18 +74,18 @@ CLASS="CHAPTER" >Chapter 27. Reporting BugsChapter 31. Reporting Bugs

27.1. Introduction31.1. Introduction

The email address for bug reports for stable releases is samba@samba.org. @@ -125,8 +125,8 @@ CLASS="SECT1" >

27.2. General info31.2. General info

Before submitting a bug report check your config for silly @@ -135,8 +135,7 @@ you've misconfigured something and run testparm to test your config file for correct syntax.

Have you run through the diagnosis? This is very important.

27.3. Debug levels31.3. Debug levels

If the bug has anything to do with Samba behaving incorrectly as a @@ -181,9 +180,15 @@ include = /usr/local/samba/lib/smb.conf.%mthen create a file /usr/local/samba/lib/smb.conf.machine/usr/local/samba/lib/smb.conf.machine where -"machine" is the name of the client you wish to debug. In that file +machine is the name of the client you wish to debug. In that file put any smb.conf commands you want, for example debuglevel = that has been used in older versions of Samba and is being retained for backwards -compatibility of smb.conf files.

smb.conf files.

As the

27.4. Internal errors31.4. Internal errors

If you get a "INTERNAL ERROR" message in your log files it means that Samba got an unexpected signal while running. It is probably a segmentation fault and almost certainly means a bug in Samba (unless -you have faulty hardware or system software)

If the message came from smbd then it will probably be accompanied by a message which details the last SMB message received by smbd. This @@ -237,7 +245,10 @@ include it in your bug report.

You should also detail how to reproduce the problem, if possible. Please make this reasonably detailed.

You may also find that a core file appeared in a "corefiles" +>You may also find that a core file appeared in a corefiles subdirectory of the directory where you keep your samba log files. This file is the most useful tool for tracking down the bug. To use it you do this:

adding appropriate paths to smbd and core so gdb can find them. If you -don't have gdb then try "dbx". Then within the debugger use the -command "where" to give a stack trace of where the problem +don't have gdb then try dbx. Then within the debugger use the +command where to give a stack trace of where the problem occurred. Include this in your mail.

If you known any assembly language then do a "disass" of the routine +>If you known any assembly language then do a disass of the routine where the problem occurred (if its in a library routine then disassemble the routine that called it) and try to work out exactly where the problem is by looking at the surrounding code. Even if you @@ -264,15 +284,30 @@ CLASS="SECT1" >

27.5. Attaching to a running process31.5. Attaching to a running process

Unfortunately some unixes (in particular some recent linux kernels) refuse to dump a core file if the task has changed uid (which smbd does often). To debug with this sort of system you could try to attach -to the running process using "gdb smbd PID" where you get PID from -smbstatus. Then use "c" to continue and try to cause the core dump +to the running process using gdb smbd PID where you get PID from +smbstatus. Then use c to continue and try to cause the core dump using the client. The debugger should catch the fault and tell you where it occurred.

27.6. Patches31.6. Patches

The best sort of bug report is one that includes a fix! If you send us -patches please use diff -udiff -u format if your version of -diff supports it, otherwise use diff -c4diff -c4. Make sure your do the diff against a clean version of the source and let me know exactly what version you used.