New MegaZeux Release FAQ: Difference between revisions
(Created page with "== All Versions == ''The new MegaZeux release has a bug that wasn't in the last release!'' Please use the [http://www.digitalmzx.net/forums/index.php?app=tracker&showproject=4 ...") |
No edit summary |
||
| Line 8: | Line 8: | ||
''I've found a bug and I want to make a good quality report. MegaZeux crashes and I've found a way to reproduce it, but I want to pass this on to developers in the best way possible. How can I achieve this?'' | ''I've found a bug and I want to make a good quality report. MegaZeux crashes and I've found a way to reproduce it, but I want to pass this on to developers in the best way possible. How can I achieve this?'' | ||
An excellent question! As of 2.82b, MegaZeux uses something called GNU debuglink to provide optional side-by-side debug packages which you can install (together with GDB) to produce something called a backtrace which is very useful to developers. This supplants an earlier project | An excellent question! As of 2.82b, MegaZeux uses something called GNU debuglink to provide optional side-by-side debug packages which you can install (together with GDB) to produce something called a backtrace which is very useful to developers. This supplants an earlier project ajs's called the "MZX Debugging Package", but its goals are the same. | ||
*Grab the symbols for your version (one of windows-x86, windows-x64, ubuntu i386 or ubuntu amd64 at the moment). For windows, these packages are called e.g. mzx283-x86.debug.zip | *Grab the symbols for your version (one of windows-x86, windows-x64, ubuntu i386 or ubuntu amd64 at the moment). For windows, these packages are called e.g. mzx283-x86.debug.zip | ||
*Extract the package to the same directory (or install the Ubuntu -dbg package). | *Extract the package to the same directory (or install the Ubuntu -dbg package). | ||
* | *[http://downloads.sourceforge.net/project/mingw/GNU%20Source-Level%20Debugger/GDB-7.0/gdb-7.0-2-mingw32-bin.tar.gz Download GDB] if you don't already have it and extract it into the MZX directory with your release and debug symbols. | ||
*Drag "megazeux.exe" over gdb.exe. | *Drag "megazeux.exe" over gdb.exe. | ||
*Type "r" and press return. | *Type "r" and press return. | ||
Revision as of 00:38, 3 June 2012
All Versions
The new MegaZeux release has a bug that wasn't in the last release!
Please use the MegaZeux bug tracker to report the new bug. If MegaZeux crashes, or doesn't work at all, cross post the issue you're having in the new version release thread as well.
I've found a bug and I want to make a good quality report. MegaZeux crashes and I've found a way to reproduce it, but I want to pass this on to developers in the best way possible. How can I achieve this?
An excellent question! As of 2.82b, MegaZeux uses something called GNU debuglink to provide optional side-by-side debug packages which you can install (together with GDB) to produce something called a backtrace which is very useful to developers. This supplants an earlier project ajs's called the "MZX Debugging Package", but its goals are the same.
- Grab the symbols for your version (one of windows-x86, windows-x64, ubuntu i386 or ubuntu amd64 at the moment). For windows, these packages are called e.g. mzx283-x86.debug.zip
- Extract the package to the same directory (or install the Ubuntu -dbg package).
- Download GDB if you don't already have it and extract it into the MZX directory with your release and debug symbols.
- Drag "megazeux.exe" over gdb.exe.
- Type "r" and press return.
- Reproduce the crash context.
- Backtrace with "bt full" and copy/paste the results to a bug report thread.
MegaZeux 2.83
The new 'glsl' video_output option doesn't work, or the quality is bad!
The new renderer will only work on video cards capable of OpenGL 2.0 or greater. There are known quality issues with glsl on some ATI Radeon cards (X1300) that will be looked into ASAP. Modern cards like HD Radeons should not be affected.