View Single Post
Old 05-21-2010   #1
K.S.
Formerly Inuyasha
Retired Staff
 
K.S.'s Avatar
Default SRB2 2.0.5 Bug Reports (Old Topic)

Yeah, yeah, you know what to do here.

If you are getting an error message, write down exactly what it says. Otherwise our crack team of coders will not be able to find it and where it's coming from. Also, if the game SIGSEGVs, not only tell us what you were doing, but check the bottom listing of errorlog.txt and post the 8-digit value after "EIP"; this is invaluable for fixing such errors.

Here is an example of where you will see the EIP which Sonict has bolded for you (thanks, Sonict!):

Quote:
Originally Posted by Example Crash
Registers:
EAX=00001fb4 CS=001b EIP=1002d121 EFLGS=00210206
EBX=00000000 SS=0023 ESP=0012fe50 EBP=005ca1b0
ECX=10047aa0 DS=0023 ESI=05fb5418 FS=003b
EDX=00001000 ES=0023 EDI=004453c0 GS=0000
If an entire bug report has been bolded, it means that the bug has been fixed. Italicized text after a bug report should be a note left by a developer. Thus, you should not be using bold nor italics in your bug reports.

If your bug report was deleted, then either it is a duplicated bug report or one that we cannot reproduce.

Like in the suggestions topic, Jazz, Spazzo and I will be going through and culling invalid bug reports and spam posts. If you have any questions, feel free to PM one of us. Also, keep in mind that with each release EIPs from the previous release are no longer valid. Be sure that the EIPs you find from errorlog.txt are from the most recent version of SRB2.

Lastly, if you're posting screenshots of an error in a SP stage, it would greatly help if you enabled DEVMODE before taking the screenshot, so that we have the exact coordinates of your location.

Moderator Notice:
Spazzo note: We are not accepting any bug reports that occurred while using OpenGL. This includes sigsegv's.

Last edited by Spazzo; 05-25-2010 at 11:50 PM.
K.S. is offline