You are not logged in.
Pages: 1
Hi zeromus,
The other night on #dsdev I asked about desmume supporting no$gba console printing, and you recommended that I just add a call to swi 0xFC, which is the ideas protocol. I did just that and it works great! The only thing is that I noticed that this call actually prints a newline every time it's made. Indeed, looking at the desmume source code, I see that IdeasLog() ends with a printf("\n").
I was wondering whether you could just remove that newline? This would allow for proper formatting; for instance, in my code, I effectively rerouted printf() to this ideasLog(), but my formatting is messed because newlines are inserted for each call.
What do you think?
Yeah, I wanted to play around with the gdbstub code to see if I could understand why it wasn't working when I would set a breakpoint or try to break from within my debugger. It seems that breaking or setting a breakpoint while the game is running doesn't send any packets to the gdbstub, so this is not necessarily a problem in the emulator. I'll keep digging.
Ok, downloaded and built DEVELOPER and GDB_STUB debug 2005 version (windows), tested the gdbstub stuff, and it seems to be working the same as 0.9.4-win32.
Btw, I'm guessing I need to sync the full source and build it to test the latest version? Or is there some way to get just the latest binaries?
I don't mind making sure it still works, just let me know when would be a good time to test it out. So I presume that in cleaning up the code, you'll not only make sure it still works, but try to address the problem I brought forth?
It's a shame that none of you use this feature as I think it's one of the best features of desmume. I guess it makes sense, though, since it's most useful for DS developers, not emu developers Thanks for the quick response!
Hi,
First I just want to say that I love this emulator! Been developing on DS, and this is the emu of choice! I especially like it for the gdb stub feature, which I find indispensable.
I've gotten many gdb debugger IDEs working so far: Insight, eclipse, CodeLite, and WinGDB. Some of these debuggers are better than others in terms of exposing or implementing certain gdb features; however, one thing does not work across all debuggers: setting breakpoints while the rom is executing. In fact, I think this generalizes to just being able to stop/pause execution at any point, which also doesn't work. I'm thinking this is a problem with the gdb stub implementation, since it doesn't work on any of the debuggers I've tried (nor from straight commandline gdb). Is this something you're aware of?
Thanks!
Pages: 1