Discussion in 'Engineering & Reverse Engineering' started by fuzzbuzz, Dec 25, 2003.
Go to downloads -> click on Gens 2.12b (current source release)
Uh huh... and that'll be your edited (DebuGens) source code, or the official Gens release? I'm thinking the latter.
Sounding a little haughty? lol I didn't know you wanted my DebugGens source.
I'll have to collect it up. btw, it's very ugly and has things that aren't implemented (hell, or even needed), so before you decide you want to start programming with it, you'll need to clean it up.
Also, I didn't comment the ASM when I changed things for layer disabling/enabling, so just don't even try to mess with it.
Hey, I've got plenty of free time. I'll fix it up. Of course, I'll have to get it to compile under GCC, 'cuz I don't have MSVC++... err... maybe I'm not the one for the job.
Hm. If you've got the Dsound.lib, dinput.lib and ddraw.lib, it shouldn't be much of a problem. Just you'll have to get it to work correctly, which I don't think it will take too much time.
Also, I figured out why it would be a hard to write a breakpoint system in Gens. Because there's a call to the 68K emulator that executes about 1000 cycles or something like that. You'll have to edit the 68K Emulator's assembly to get the program execution to stop when the PC reaches the breakpoint.
Don't try to catch the breakpoint after the execution of the 68k cycles. It would be an easy fix, but the registers and memory values wouldn't be that same as if the breakpoint was executed at the value it's set at. The extra instructions executed after the breakpoint would change them.
So yea, use assembly all the way for the breakpoint system.
Okay, does anybody wanna help me with this? fuzzbuzz wants to work alone, and I can't do it by myself. Here's my plan:
Phase 1) Acquire source code. Duh.
Phase 2) Set up CVS. This might be hard, considering that my dev station isn't connected to the Internet. May skip, but this could be importiant for keeping in contact with each other.
Phase 3) Profit!
Phase 4) Reformat code to compile under GCC. This may require a fork, and a LOT of work. I will NOT use MSVC++. Sorry, but thems the breaks.
Phase 5) Rewrite emulator code to stop when a breakpoint is set, and add step, backstep, and on-the-fly edit features.
Phase 6) Test.
Phase 7) Release.
Phase 8) Profit!
Yeah. Anyone here know C/C++ and/or x86 ASM and wants to help me, respond.
Yeah it's a violation of the GPL licence Gens is released under not to provide source code for modified versions. Actually I'm not sure if LOst ever provided the source for his "sGens".
He's not in violation. If anyone wants the code, they could ask him and he'll provide it. I hope.
Well, at this point in time, _I_ have no binary posted on the internet...so technically, I don't have to release the code. Come to think of it, if I never put a binary of debuGens on my site, I never have to release the code. dundundun...
But why would I go do a thing like that? :P
Oh, and don't give speeches on the GPL. It's really annoying and inspires me to not want to work on any project under it...even though I love the GPL. Seriously. I'm not an asshole, and I'll release source, just I like to release things that people can use and/or understand.
Sorry I was just merely clarifying that you have to release the source (since I've known other people who didn't realise this), I just wouldn't want you to suddenly find the gens author angry at you or anything.
I figured you weren't out to get me or anything. :P I just hear alot about the GPL from people who seem very haughty.
btw, Stef doesn't seem to be too interested if someone does or doesn't release source to their modification. I've noticed this in the gens forums when people post their mods and not the source along with it. :o
This file needs a new mirror, I guess. Where could I get the lastest version of DebuGens?
Separate names with a comma.