Project

General

Profile

Actions

HowToReportABug » History » Revision 2

« Previous | Revision 2/16 (diff) | Next »
jan, 2005-08-22 16:18
added a comment for strace -p


= How to report a bug =

If you find a bug in lighttpd you can help alot to find a fix for it by following some simple steps:

Backtrace

A backtrace is a trace of the function which have been called before lighttpd died.

The best way to generate such a backtrace is using [http://valgrind.kde.org/ valgrind]:

{{{
$ valgrind --tool=memcheck -v --logfile=lighttpd --num-callers=8 lighttpd -D -f ./lighttpd.conf
}}}

valgrind does many useful things while it waits for the server to crash:

  • checks for uninitialized variables * checks for out-of-bounds access * and many more

If you can't use valgrind there is another way to generate a backtrace:

{{{
$ gdb lighttpd
(gdb) r -D -f lighttpd.conf
...
(gdb) bt
}}}

strace

strace is the name of the syscall-tracer on Linux. Every Unix-like OS provides a utility to collect information about system call like open, write, close and so on.

The have different names like

  • strace * truss * ktrace (then kdump to get output)

If strace is available it is prefered as it provides the most useful information. Execute it like:

{{{
$ strace -olighttpd.trace -tt -s 4000 lighttpd -D -f ./lighttpd.conf
}}}

It will generate a file called lighttpd.trace.

If you have a running instance of lighttpd and want to see what lighttpd is doing you can attach strace to the process:

{{{
$ strace -olighttpd.trace -tt -s 4000 -p <pidof-lighttpd>
}}}

Writing a bug report

If you have generated a backtrace or a syscall-trace please make sure that you can reproduce the problem. Otherwise it will be really hard for the developers to fix the problem for you.

If possible open a [http://trac.lighttpd.net/trac/newticket new ticket]

If the report contains sensitive data you might also send it directly to: mailto:

Updated by jan almost 15 years ago · 2 revisions