5 The FreeRADIUS web site is at <URL: http://www.freeradius.org>, and
6 most information referenced in this document can be found there.
8 This is primarily for non-developers of the FreeRADIUS server. If you are
9 able to patch the code to work correctly, then we invite you to join the
10 development list to discuss it. If you're the type who know little about
11 how to code, then this is the place for you!
15 So you think you've found a bug in the FreeRADIUS server?
17 You should first discuss it on the users list, to see if anyone can
18 reproduce it. Often there's a simple explanation of why the server
19 behaves as it does, and it's not necessarily a bug in the code, so
20 browse the lists' archives of the last two months, and if you don't
21 see messages about it, ask!
23 If the behavior is correct but confusing, we think that's a bug too, and
24 you should file a bug against our documentation.
26 For more information about the users list, the lists' archives and the
27 faq, please visit http://www.freeradius.org/list/users.html
28 Please make sure to READ and RESPECT the house-rules. You will get much
29 better response and much faster if you do!
33 If the server, or one of the accompyaning programs core dumps, then
34 you should rebuild the server as follows:
36 $ ./configure --enable-developer
40 and then run the program again. You may have to to enable core
45 When it core dumps, do:
47 $ gdb /path/to/executable /path/to/core/file
49 And then in 'gdb', do:
53 Copy the output, and mail it to the list, along with the name of the
54 program you were running, and the name of the operating system.
55 Without this information, it's impossible for anyone to know why the
58 You can also submit the information to the bug database at:
60 http://bugs.freeradius.org/
62 Submitting it to the bug database ensures that the bug report won't
63 get forgotten, and that someone will eventually respond to it.
67 FreeRADIUS Project, copyright 2004