Acorn Arcade forums: Programming: ARM debugger
| |
ARM debugger |
| |
Michelfasen (13:18 5/4/2002)
Loris (15:35 5/4/2002)
andreww (22:49 5/4/2002)
gareth3 (17:38 8/6/2003)
tribbles (07:34 9/6/2003)
|
| |
|
Michel Fasen |
Message #86233, posted by Michelfasen at 13:18, 5/4/2002 |
AA refugee
Posts: 1
|
I'm currently working on an ARM deb****r. It works and I use it myself to debug assembler programs. Is anyone interested in a ARM deb****r? Please mail me if you you're interested. I'm in the need of ideas.... |
| |
 [ Log in to reply ] |
| |
|
Tony Haines |
Message #86234, posted by Loris at 15:35, 5/4/2002, in reply to message #86233 |
 Ha ha, me mine, mwahahahaha
Posts: 1025
|
debug*ers are a bit sp*rse on the Acorn. The integrated one is fit to be scr*pped now. If you would pas* this on I would be grateful.
Sorry, just messin' with ya (and the swear-word filter).
I really would like to try this out.Yours,
Tony |
| |
[ Log in to reply ] |
| |
|
Andrew |
Message #86235, posted by andreww at 22:49, 5/4/2002, in reply to message #86234 |
AA refugee
Posts: 555
|
David McEwen wants a deb****r. |
| |
[ Log in to reply ] |
| |
|
gareth |
Message #86236, posted by gareth3 at 17:38, 8/6/2003, in reply to message #86235 |
AA refugee
Posts: 5
|
A lot of deb****rs I've used seem to disassemble the code, which I personally find is useless, because you can't actually see which instruction(s) are changing a specifc register's value. Therefore, what I would find useful is a deb****r that cycles through a display of the the 'actual' ARM Code i.e. unaltered, displaying the values passed to each register, as well as informing the programmer where any error is occurring. Probably the best example I have seen of this type of code deb****r is in Visual C++.
If your deb****r works like this then I would be interested.
[Edited by gareth at 18:41, 8/6/2003] |
| |
[ Log in to reply ] |
| |
|
Jason Tribbeck |
Message #86237, posted by tribbles at 07:34, 9/6/2003, in reply to message #86236 |
 Captain Helix
Posts: 929
|
A lot of deb****rs I've used seem to disassemble the code, which I personally find is useless, because you can't actually see which instruction(s) are changing a specifc register's value. Therefore, what I would find useful is a deb****r that cycles through a display of the the 'actual' ARM Code i.e. unaltered, displaying the values passed to each register, as well as informing the programmer where any error is occurring. If you can't tell what's happening when you do MOV r1, r2, LSL#3, then you really shouldn't be programming in ARM code, yet alone debugging it  . Even with the most difficult of instructions (probably LDM/STM) you should be able to work out what's going on. Having said that, knowing what the outcome would be before running the instruction would be handy in some circumstances (notably when you don't have a calculator to hand [when the numbers are difficult]). I've found that the best pure ARM deb****r was QDBug, but that doesn't work on RISC OS 3.5 or later (wasn't updated for RiscPC). |
| |
[ Log in to reply ] |
| |
|
Acorn Arcade forums: Programming: ARM debugger |
