+  RHDN Forum Archive
|-+  Romhacking
| |-+  ROM Hacking Discussion
| | |-+  Gens Tracer Help needed
Pages: [1]
Author Topic: Gens Tracer Help needed  (Read 2 times)
artefactman
Guest
« on: January 17, 2009, 10:19:57 am »
I'm trying to crack compression in a Genesis game, I used Gens2.12aR2Tracer to log CPU instructions into a file. But I've a problem : when an instruction which have been already logged is reexecuted, the instruction isn't logged again. I've some difficult in english and the software isn't very easy to use. I tried to find a way to log all instructions but I never success :

How can I log all CPU instructions with Gens2.12aR2Tracer ?

The algorithm I try to crack seems to be very complex.

If it cannot be done, is there another way to trace CPU instructions ?
RedComet
Guest
« Reply #1 on: January 17, 2009, 11:15:19 am »
What game are you working on?

To answer your question, use the hook_log. Place the start address of the code and instead of specifying an end address leave it as -1. That will cause the program to log every instruction after the start address. Hope that helps.
artefactman
Guest
« Reply #2 on: January 19, 2009, 10:11:18 am »
Code:
.....
00:5CA2  6D E4  BLT     #$E4 [00:5C88]           
00:5CA4  4A 87  TST.L   D7                     
00:5CA6  6A 00  BPL     #$FFFFFE0C [00:5AB4] 

///--> I want 5AB4 & more instructions here (5AB4 has been executed before)

00:5BF4  76 00  MOVEQ   #$00,D3
.....



In my hook_log.txt :

Code:
hook_pc1 1 005a7a -1

Is that correct ? (0x5a7a = adress of the code segment I want to work on)
Because it logs instructions at 0x4826, etc...

I'm working on Thunder Force III, the decompression process is very long, and the routine is horrible.
I have some problems with the log, I run two logging process and only one success, the other don't run :

Code:
00:5FF8  32 BC  MOVE.w  #$EFB4,(A1)           
00:5FFC  60 2A  BRA     #$2A [00:6028]           

TRACE STOPPED

----> NOTHING ?????

TRACE STOPPED
« Last Edit: January 19, 2009, 10:23:30 am by artefactman »
RedComet
Guest
« Reply #3 on: January 19, 2009, 11:34:46 am »
You'll have to turn the hook log on (the ',' key) and the code will be logged to hook.txt instead of trace.txt. That's the only thing I can think of that you might be doing. Your hook_log is correct.
BigNailCow
Guest
« Reply #4 on: March 26, 2009, 05:12:54 pm »
I doubt you're still messing with this, but I just saw the topic.  If you press the / key it will toggle verbosity.  It starts on for me, so I don't know if that's the problem.
Pages: [1]  


Powered by SMF 1.1.4 | SMF © 2006-2007, Simple Machines LLC