(11-03-2009, 01:48 AM)revel8n Wrote: Hello,
i have been attempting to do some debugging lately and having come from visual studio and ida pro i had a few things i would like to suggest:
- Break on register value. i have hacked this into the interpreter mode at the moment, but unfortunately as my values are hard coded i cannot change them on the fly through the interface. Being able to have the emulation break when the register contains a particular value would be extremely useful.
- Conditional breakpoints. Somewhat of an extension of the above, not as necessary but would be nice.
- Hex dump style memory views. For me the memory values being segmented into 32-bit values by default is not always as useful, especially if you are comparing against external data in a hex editor. There is always dumping to file, but seeing as you step through the code can be helpful.
- Memory seaching. Being able to search memory directly would be useful as well, but i guess not as necessary when you can do a memory dump. As with the previous being able to see it as you are stepping through would be nice.
- Hardware access break points. i left the title of this one fairly general, but my main goal here is to be able to detect when certain data is accessed from the file system. Either by file name and possibly even by file/sector offset, etc. Since games that use pak files cannot contain the entire data file in memory, often times the many instances where a particular file is accessed is not important to me until a particular section of data from the file is retrieved. Being able to determine when this occurs and track where it is accessed in code and memory would be a very helpful support tool in addition to memory break point usage.
- Is there any way to improve the debugging capabilities of JIT mode, or to possibly speed up interpret mode? Heh, just curious.
For now i guess i will attempt to work out how to hack in support for some of these as i did with the register breakpoint, but more officially integrated debugging tools would definitely be beneficial to me.
Thanks in advance.
Maybe asking to one of the developers about WxWidgets might help you, is adding some fields to the breakpoints window to specify special conditions what you need?
Got that running by comparing memory dumps and values (which takes minutes), never managed to perform direct memory searches.
Made a patch, but it is extremely outdated.
ASRock Conroe 1333-D667
Intel Pentium Dual Core E2180 2.00GHZ
2GB ram
Windows XP x64
Ati Radeon HD3650 256mb GDDR3
Intel Pentium Dual Core E2180 2.00GHZ
2GB ram
Windows XP x64
Ati Radeon HD3650 256mb GDDR3
![[Image: bugwk7.gif]](http://img503.imageshack.us/img503/301/bugwk7.gif)

![[Image: 670320.png]](http://valid.canardpc.com/cache/banner/670320.png)


![[Image: youtube.png]](http://www.hosteev.com/img/youtube.png)
