blob: 2653ffd74e6e599f841f80244ac4b31b2cc4a6cb [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "">
<html lang="en">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<title>Mesa Bug Reporting</title>
<link rel="stylesheet" type="text/css" href="mesa.css">
<div class="header">
<h1>The Mesa 3D Graphics Library</h1>
<iframe src="contents.html"></iframe>
<div class="content">
<h1>Report a bug</h1>
The Mesa bug database is hosted on
<a href=""></a>.
The old bug database on SourceForge is no longer used.
To file a Mesa bug, go to
<a href="">
Bugzilla on</a>
Please follow these bug reporting guidelines:
<li>Check if a new version of Mesa is available which might have fixed
the problem.
<li>Check if your bug is already reported in the database.
<li>Monitor your bug report for requests for additional information, etc.
<li>Attach the output of running glxinfo or wglinfo.
This will tell us the Mesa version, which device driver you're using, etc.
<li>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.
<li>Describe in detail how to reproduce the bug, especially with games
and applications that the Mesa developers might not be familiar with.
<li>Provide an <a href="">apitrace</a>
or simple GLUT-based test program if possible.
Bug reports will automatically be forwarded by bugzilla to the Mesa
developer's mailing list.
The easier a bug is to reproduce, the sooner it will be fixed.
Please do everything you can to facilitate quickly fixing bugs.
If your bug report is vague or your test program doesn't compile
easily, the problem may not be fixed very quickly.