diff options
Diffstat (limited to 'docs/htmldocs/bugreport.html')
| -rw-r--r-- | docs/htmldocs/bugreport.html | 175 |
1 files changed, 48 insertions, 127 deletions
diff --git a/docs/htmldocs/bugreport.html b/docs/htmldocs/bugreport.html index ac0fac371f..fcc4b7e91a 100644 --- a/docs/htmldocs/bugreport.html +++ b/docs/htmldocs/bugreport.html @@ -5,7 +5,8 @@ >Reporting Bugs</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ +"><LINK REL="HOME" TITLE="SAMBA Project Documentation" HREF="samba-howto-collection.html"><LINK @@ -13,8 +14,11 @@ REL="UP" TITLE="Appendixes" HREF="appendixes.html"><LINK REL="PREVIOUS" -TITLE="Analysing and solving samba problems" -HREF="problems.html"></HEAD +TITLE="Samba and other CIFS clients" +HREF="other-clients.html"><LINK +REL="NEXT" +TITLE="Diagnosing your samba server" +HREF="diagnosis.html"></HEAD ><BODY CLASS="CHAPTER" BGCOLOR="#FFFFFF" @@ -42,7 +46,7 @@ WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A -HREF="problems.html" +HREF="other-clients.html" ACCESSKEY="P" >Prev</A ></TD @@ -55,7 +59,11 @@ VALIGN="bottom" WIDTH="10%" ALIGN="right" VALIGN="bottom" -> </TD +><A +HREF="diagnosis.html" +ACCESSKEY="N" +>Next</A +></TD ></TR ></TABLE ><HR @@ -65,59 +73,16 @@ WIDTH="100%"></DIV CLASS="CHAPTER" ><H1 ><A -NAME="BUGREPORT" -></A ->Chapter 35. Reporting Bugs</H1 -><DIV -CLASS="TOC" -><DL -><DT -><B ->Table of Contents</B -></DT -><DT ->35.1. <A -HREF="bugreport.html#AEN5125" ->Introduction</A -></DT -><DT ->35.2. <A -HREF="bugreport.html#AEN5135" ->General info</A -></DT -><DT ->35.3. <A -HREF="bugreport.html#AEN5141" ->Debug levels</A -></DT -><DT ->35.4. <A -HREF="bugreport.html#AEN5162" ->Internal errors</A -></DT -><DT ->35.5. <A -HREF="bugreport.html#AEN5176" ->Attaching to a running process</A -></DT -><DT ->35.6. <A -HREF="bugreport.html#AEN5184" ->Patches</A -></DT -></DL -></DIV +NAME="BUGREPORT">Chapter 25. Reporting Bugs</H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN5125" ->35.1. Introduction</A -></H1 +NAME="AEN3309">25.1. Introduction</H1 ><P >The email address for bug reports for stable releases is <A -HREF="mailto:samba@samba.org" +HREF="samba@samba.org" TARGET="_top" >samba@samba.org</A >. @@ -157,9 +122,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN5135" ->35.2. General info</A -></H1 +NAME="AEN3319">25.2. General info</H1 ><P >Before submitting a bug report check your config for silly errors. Look in your log files for obvious messages that tell you that @@ -167,7 +130,8 @@ you've misconfigured something and run testparm to test your config file for correct syntax.</P ><P >Have you run through the <A -HREF="diagnosis.html" +HREF="Diagnosis.html" +TARGET="_top" >diagnosis</A >? This is very important.</P @@ -181,9 +145,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN5141" ->35.3. Debug levels</A -></H1 +NAME="AEN3325">25.3. Debug levels</H1 ><P >If the bug has anything to do with Samba behaving incorrectly as a server (like refusing to open a file) then the log files will probably @@ -212,19 +174,10 @@ include = /usr/local/samba/lib/smb.conf.%m</PRE >then create a file <TT CLASS="FILENAME" ->/usr/local/samba/lib/smb.conf.<VAR -CLASS="REPLACEABLE" ->machine</VAR -></TT +>/usr/local/samba/lib/smb.conf.machine</TT > where -<VAR -CLASS="REPLACEABLE" ->machine</VAR -> is the name of the client you wish to debug. In that file -put any <TT -CLASS="FILENAME" ->smb.conf</TT -> commands you want, for example +"machine" is the name of the client you wish to debug. In that file +put any smb.conf commands you want, for example <B CLASS="COMMAND" >log level=</B @@ -244,10 +197,7 @@ CLASS="COMMAND" >debuglevel =</B > that has been used in older versions of Samba and is being retained for backwards -compatibility of <TT -CLASS="FILENAME" ->smb.conf</TT -> files.</P +compatibility of smb.conf files.</P ><P >As the <B CLASS="COMMAND" @@ -263,14 +213,12 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN5162" ->35.4. Internal errors</A -></H1 +NAME="AEN3342">25.4. Internal errors</H1 ><P >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).</P +you have faulty hardware or system software)</P ><P >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 @@ -280,10 +228,7 @@ include it in your bug report.</P >You should also detail how to reproduce the problem, if possible. Please make this reasonably detailed.</P ><P ->You may also find that a core file appeared in a <TT -CLASS="FILENAME" ->corefiles</TT -> +>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:</P @@ -294,20 +239,11 @@ CLASS="COMMAND" ></P ><P >adding appropriate paths to smbd and core so gdb can find them. If you -don't have gdb then try <KBD -CLASS="USERINPUT" ->dbx</KBD ->. Then within the debugger use the -command <KBD -CLASS="USERINPUT" ->where</KBD -> 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.</P ><P ->If you known any assembly language then do a <KBD -CLASS="USERINPUT" ->disass</KBD -> 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 @@ -319,30 +255,13 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN5176" ->35.5. Attaching to a running process</A -></H1 +NAME="AEN3352">25.5. Attaching to a running process</H1 ><P >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 <KBD -CLASS="USERINPUT" ->gdb smbd <VAR -CLASS="REPLACEABLE" ->PID</VAR -></KBD -> where you get <VAR -CLASS="REPLACEABLE" ->PID</VAR -> from -<SPAN -CLASS="APPLICATION" ->smbstatus</SPAN ->. Then use <KBD -CLASS="USERINPUT" ->c</KBD -> 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.</P ></DIV @@ -351,18 +270,16 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN5184" ->35.6. Patches</A -></H1 +NAME="AEN3355">25.6. Patches</H1 ><P >The best sort of bug report is one that includes a fix! If you send us -patches please use <KBD -CLASS="USERINPUT" ->diff -u</KBD +patches please use <B +CLASS="COMMAND" +>diff -u</B > format if your version of -diff supports it, otherwise use <KBD -CLASS="USERINPUT" ->diff -c4</KBD +diff supports it, otherwise use <B +CLASS="COMMAND" +>diff -c4</B >. Make sure your do the diff against a clean version of the source and let me know exactly what version you used. </P @@ -384,7 +301,7 @@ WIDTH="33%" ALIGN="left" VALIGN="top" ><A -HREF="problems.html" +HREF="other-clients.html" ACCESSKEY="P" >Prev</A ></TD @@ -401,14 +318,18 @@ ACCESSKEY="H" WIDTH="33%" ALIGN="right" VALIGN="top" -> </TD +><A +HREF="diagnosis.html" +ACCESSKEY="N" +>Next</A +></TD ></TR ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" ->Analysing and solving samba problems</TD +>Samba and other CIFS clients</TD ><TD WIDTH="34%" ALIGN="center" @@ -422,7 +343,7 @@ ACCESSKEY="U" WIDTH="33%" ALIGN="right" VALIGN="top" -> </TD +>Diagnosing your samba server</TD ></TR ></TABLE ></DIV |