| 1 | Report a Bug
|
|---|
| 2 | ============
|
|---|
| 3 |
|
|---|
| 4 | To file a Mesa bug, go to `GitLab on
|
|---|
| 5 | freedesktop.org <https://gitlab.freedesktop.org/mesa/mesa/-/issues>`__.
|
|---|
| 6 |
|
|---|
| 7 | Please follow these bug reporting guidelines:
|
|---|
| 8 |
|
|---|
| 9 | - Check if a new version of Mesa is available which might have fixed
|
|---|
| 10 | the problem.
|
|---|
| 11 | - Check if your bug is already reported in the database.
|
|---|
| 12 | - Monitor your bug report for requests for additional information, etc.
|
|---|
| 13 | - Attach the output of running glxinfo or wglinfo. This will tell us
|
|---|
| 14 | the Mesa version, which device driver you're using, etc.
|
|---|
| 15 | - If you're reporting a crash, try to use your debugger (gdb) to get a
|
|---|
| 16 | stack trace. Also, recompile Mesa in debug mode to get more detailed
|
|---|
| 17 | information.
|
|---|
| 18 | - Describe in detail how to reproduce the bug, especially with games
|
|---|
| 19 | and applications that the Mesa developers might not be familiar with.
|
|---|
| 20 | - Provide an `apitrace <https://github.com/apitrace/apitrace>`__ or
|
|---|
| 21 | simple GLUT-based test program if possible.
|
|---|
| 22 |
|
|---|
| 23 | The easier a bug is to reproduce, the sooner it will be fixed. Please do
|
|---|
| 24 | everything you can to facilitate quickly fixing bugs. If your bug report
|
|---|
| 25 | is vague or your test program doesn't compile easily, the problem may
|
|---|
| 26 | not be fixed very quickly.
|
|---|
