]>
Commit | Line | Data |
---|---|---|
718e3744 | 1 | This file describes the procedure for reporting Zebra bugs. |
2 | You are not obliged to follow this format , but it would be | |
3 | great help for Zebra developers if you report a bug as described | |
4 | below. | |
5 | ||
6 | Send your report to bug-zebra@gnu.org mailing list. | |
7 | ||
8 | Please supply the following information: | |
9 | 1. Your zebra version or if it is CVS version then the date you did checkout. | |
10 | Always try to report the bugs on the current CVS version. | |
11 | 2. Zebra daemons you run e.g. bgpd or ripd, your OS full name, | |
12 | any specific options you compiled zebra with. | |
13 | 3. Problem description. Copy and paste relative zebra commands and their | |
14 | output to describe your network setup e.g. "zebra>show ip route". | |
15 | Please, also give your simple network layout and output of relative OS commands | |
16 | (e.g. ifconfig). | |
17 | 4. All zebra configuration files you use. If you don't want to publish | |
18 | your network numbers change 2 middle bytes in IPv4 address to be XXX e.g. | |
19 | 192.XXX.XXX.32/24. Similar could be done with IPv6. | |
20 | 5. If any zebra daemon core dumped, please, supply stack trace using | |
21 | the following commands: host> gdb exec_file core_file , (gdb) bt . | |
22 | 6. Run all zebra daemons with full debugging on (see documentation on debugging) and | |
23 | send _only_ part of logs which are relative to your problem. | |
24 | 7. If the problem is difficult to reproduce please send a shell script to | |
25 | reproduce it. | |
26 | 8. Patches, workarounds, fixes are always welcome. | |
27 | ||
28 | Thank You. |