Posted: Tue Feb 17, 2015 9:58 am
About hacking:
from my personnal experience, I recommand using IDA+M.IDA and help you with GensKMod
http://gendev.spritesmind.net/page-nhl94.html
http://gendev.spritesmind.net/page-mida.html
for this, you need to understood how Genny works and to be able to read 68000 assembly
One useful feature if you want to hack gfx is to activate the "DMA Spy" on KMod to get addresses and use your disassembly to find what and how gfx are load from/to these adresses
One thing to note:
Last version of KMod on Bitbucket fixed a lot of bugs and added some great features (like planes and pre-gdb) but also added a very annoying bug (crash a lot)
About GDB:
Graz only use DDD and not GDB
I know GDB use several ways to communicate with the stub
I tried with Stef to make a useful gdb but it seems that
1/ gdb stub is broken
2/ debug version of a rom is wrongly linked
About message
I know
It's just that I didn't find a way to handle an infinite message listing...
Whatever I try fill up memory OR I lose the ability to log on a file
I mainly related to my lack of knowledge on this area on WinAPI
I never found the time to look at these 3 bugs (crash, gdb and message)
But it's also why KMod is open source
At this time, only Graz got involved on KMod which is a shame...but I'm now used to this
I'll finish on a good news :
since the crash REALLY annoys me for my current projects, I may try to fix it "soon"
from my personnal experience, I recommand using IDA+M.IDA and help you with GensKMod
http://gendev.spritesmind.net/page-nhl94.html
http://gendev.spritesmind.net/page-mida.html
for this, you need to understood how Genny works and to be able to read 68000 assembly
One useful feature if you want to hack gfx is to activate the "DMA Spy" on KMod to get addresses and use your disassembly to find what and how gfx are load from/to these adresses
One thing to note:
Last version of KMod on Bitbucket fixed a lot of bugs and added some great features (like planes and pre-gdb) but also added a very annoying bug (crash a lot)
About GDB:
Graz only use DDD and not GDB
I know GDB use several ways to communicate with the stub
I tried with Stef to make a useful gdb but it seems that
1/ gdb stub is broken
2/ debug version of a rom is wrongly linked
About message
I know
It's just that I didn't find a way to handle an infinite message listing...
Whatever I try fill up memory OR I lose the ability to log on a file
I mainly related to my lack of knowledge on this area on WinAPI
I never found the time to look at these 3 bugs (crash, gdb and message)
But it's also why KMod is open source
At this time, only Graz got involved on KMod which is a shame...but I'm now used to this
I'll finish on a good news :
since the crash REALLY annoys me for my current projects, I may try to fix it "soon"