blob: 4397339e968d422717c9a3cd9c905b801a22b2f5 [file] [log] [blame]
Brian Paul0b27ace2003-03-08 17:38:57 +00001<HTML>
2
3<TITLE>Mesa Bug Reporting</TITLE>
4
Brian Paul36da0452005-01-20 03:55:10 +00005<link rel="stylesheet" type="text/css" href="mesa.css"></head>
6
7<BODY>
Brian Paul0b27ace2003-03-08 17:38:57 +00008
9<H1>Bug Database</H1>
10
11<p>
Brian9ceff4a2007-09-05 10:03:32 -060012The Mesa bug database is hosted on
13<a href="http://freedesktop.org" target="_parent">freedesktop.org</a>.
14The old bug database on SourceForge is no longer used.
Brian Paul6bca16b2004-11-27 19:42:16 +000015</p>
Brian Paulddfd2062004-12-05 18:03:21 +000016
Brian Paul6bca16b2004-11-27 19:42:16 +000017<p>
Brian Paulddfd2062004-12-05 18:03:21 +000018To file a Mesa bug, go to
19<a href="https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa"
20target="_parent">
21Bugzilla on freedesktop.org</a>
22</p>
23
24<p>
25Please follow these bug reporting guidelines:
Brian Paul0b27ace2003-03-08 17:38:57 +000026</p>
27
28<ul>
Brian9ceff4a2007-09-05 10:03:32 -060029<li>Check if a new version of Mesa is available which might have fixed
30the problem.
31<li>Check if your bug is already reported in the database.
32<li>Monitor your bug report for requests for additional information, etc.
33<li>If you're reporting a crash, try to use your debugger (gdb) to get a stack
34trace. Also, recompile Mesa in debug mode to get more detailed information.
35<li>Describe in detail how to reproduce the bug, especially with games
36and applications that the Mesa developers might not be familiar with.
Brian Paul0b27ace2003-03-08 17:38:57 +000037<li>Provide a simple GLUT-based test program if possible
Brian Paul0b27ace2003-03-08 17:38:57 +000038</ul>
39
40<p>
Brian9ceff4a2007-09-05 10:03:32 -060041Bug reports will automatically be forwarded by bugzilla to the Mesa
42developer's mailing list.
Brian Paul0b27ace2003-03-08 17:38:57 +000043</p>
44
45<p>
46The easier a bug is to reproduce, the sooner it will be fixed.
47Please do everything you can to facilitate quickly fixing bugs.
48If your bug report is vague or your test program doesn't compile
49easily, the problem may not be fixed very quickly.
50</p>
51
52</BODY>
53</HTML>