X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=docs%2Fbugs.html;h=4397339e968d422717c9a3cd9c905b801a22b2f5;hb=3bee900a720685a96b39ce25307197512e457b6e;hp=9ced9dc8c2d87384e779becc0f16e61686be5975;hpb=0b27aceae2464db3dd149cf4fd667e353a655c5e;p=mesa.git diff --git a/docs/bugs.html b/docs/bugs.html index 9ced9dc8c2d..4397339e968 100644 --- a/docs/bugs.html +++ b/docs/bugs.html @@ -2,26 +2,44 @@ Mesa Bug Reporting - + + +

Bug Database

-Bug reports can be filed in the Bug -Database on sourceforge.net. Please follow these guidelines: +The Mesa bug database is hosted on +freedesktop.org. +The old bug database on SourceForge is no longer used. +

+ +

+To file a Mesa bug, go to + +Bugzilla on freedesktop.org +

+ +

+Please follow these bug reporting guidelines:

Make sure you're using the most recent version of Mesa -
Make sure your bug isn't already reported -
Include as much information as possible in the report +
Check if a new version of Mesa is available which might have fixed +the problem. +
Check if your bug is already reported in the database. +
Monitor your bug report for requests for additional information, etc. +
If you're reporting a crash, try to use your debugger (gdb) to get a stack +trace. Also, recompile Mesa in debug mode to get more detailed information. +
Describe in detail how to reproduce the bug, especially with games +and applications that the Mesa developers might not be familiar with.
Provide a simple GLUT-based test program if possible -
Check back for follow-ups to the report

-Bug reports will automatically be forwarded to the Mesa developer's list. +Bug reports will automatically be forwarded by bugzilla to the Mesa +developer's mailing list.