Based on this report
I suggest the following approach, which can be also useful for other scenarios and other "non-coders" collaborators to better find and isolate bugs, making things less harder for us coders (speacially when we haven't the same setup and/or tools to proper debug and reproduce the issues reported by some of you ;-)
Originally Posted by RandQalan
Go to the Bitbucket site
Type "644" (the last revision without the issue, as reported by you) at "Find commits box" and press [Enter]:
Now we know the related commit of this specific revision (revision 644 = commit be88f55).
Now let's take a look on 645, the one when the issue started to appear for you.
hg clone -r be88f55 https://firstname.lastname@example.org/doctorxyz/open-ps2-loader
Type "645" at "Find commits box" and press [Enter]:
Click on "d67fe19" (this is the rev645 commit label):
You notice the "Commits / d67fe19 ... doctorxyz committed ... days ago (raw commit)" text.
Click on "raw commit", in order to the see the complete diff file (http://en.wikipedia.org/wiki/Diff):
Don't panic, okay! :-D
The changes are made per source code file, always started by a diff sentence. Like this slice, which is related to the INGAME_DRIVER flag (NB: this excerpt is just an example):
The deleted row starts with a - (minus) signal, and the included row starts with + (plus) signal. All other lines remain unchanged, they exist only for give a context for the "patch" program which I explain below.
diff -r be88f55ed26f3fdb6051c7390739c85d08cde03f -r d67fe19bec603c46d2127cf7f22bd2f8dd9c59b6 Makefile
--- a/Makefile Mon Aug 13 06:00:01 2012 -0300
+++ b/Makefile Wed Jan 02 12:49:10 2013 -0200
@@ -67,7 +67,7 @@
VMC_FLAGS = VMC=0
-SMSTCPIP_INGAME_CFLAGS = INGAME_DRIVER=1
+SMSTCPIP_INGAME_CFLAGS = INGAME_DRIVER=0
MOD_DEBUG_FLAGS = DEBUG=1
If we save the above example slice as "rev644_ingame_driver_to_0.patch", for instance, we could apply this patch to rev644, using a command like this (supposing that the patch file is placed one level up, in your directory structure):
Now you can compile and test it:
patch -p1 < "../rev644_ingame_driver_to_0.patch"
Note that you can do this approach and repeated them several times with any rev and any slice, until you find the "culprit" one and report for us coders in a more detailed way.
Now I gotta go.