Chapter 35. Reporting Bugs

Jelmer R. Vernooij

The Samba Team

<jelmer@samba.org>

Someone; Tridge or Karl Auer perhaps?

27 June 1997

Table of Contents

Introduction
General info
Debug levels
Internal errors
Attaching to a running process
Patches

Introduction

Please report bugs using +Chapter 35. Reporting Bugs

Chapter 35. Reporting Bugs
Prev	Part V. Troubleshooting	Next

Chapter 35. Reporting Bugs

Jelmer R. Vernooij

The Samba Team

<jelmer@samba.org>

Someone; Tridge or Karl Auer perhaps?

27 June 1997

Table of Contents

Introduction
General info
Debug levels
Internal errors
Attaching to a running process
Patches

Introduction

Please report bugs using bugzilla.

Please take the time to read this file before you submit a bug report. Also, please see if it has changed between releases, as we @@ -21,23 +20,23 @@ that list that may be able to help you. You may also like to look though the recent mailing list archives, which are conveniently accessible on the Samba web pages at http://samba.org/samba/. -

General info

Before submitting a bug report check your config for silly errors. Look in your log files for obvious messages that tell you that you've misconfigured something and run testparm to test your config file for correct syntax.

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

If you include part of a log file with your bug report then be sure to annotate it with exactly what you were doing on the client at the time, and exactly what the results were. -

Debug levels

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 be very useful. Depending on the problem a log level of between 3 and -10 showing the problem may be appropriate. A higher level givesmore +10 showing the problem may be appropriate. A higher level gives more detail, but may use too much disk space.

To set the debug level use the log level in your @@ -68,7 +67,7 @@ debugging operations you may not need a setting higher than 3. Nearly all bugs can be tracked at a setting of 10, but be prepared for a VERY large volume of log data. -

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 @@ -99,9 +98,9 @@ If you know any assembly language then do a 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 -don't know assembly then incuding this info in the bug report can be +don't know assembly, including this info in the bug report can be useful. -

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 @@ -111,7 +110,7 @@ to the running process using 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. -

Patches

The best sort of bug report is one that includes a fix! If you send us patches please use diff -u format if your version of diff supports it, otherwise use diff -c4. Make sure -- cgit