| ??? 05/17/06 09:04 Read: times |
#116359 - implementing breakpoints Responding to: ???'s previous message |
On monday afternoon I had a very fruitful discussion with my mentor on this subject. Some sort of breakpoints will have to be added in future so user programs can jump into the debugger if needed.
I have some things in mind: a) breakpoint definable in memory by the monitor This will mean using selfmodifying code and implies use on systems with RAM. b) user breakpoints defined in the source via the assembler Either by defining a jump to the start of amon52 which generates an warmstart or by the means of a special breakpoint macro. The later one will offer the option to give the breakpoint a name and will print thsi on the console when jumped to e.q. Breakpoint 01 reached. PC DPTR ... Any ideas and suggestions welcome! |
| Topic | Author | Date |
| amon52 (work in progress) | 01/01/70 00:00 | |
| v0.4 released | 01/01/70 00:00 | |
| implementing breakpoints | 01/01/70 00:00 | |
| breakpoints in monitors | 01/01/70 00:00 | |
| breakpoints | 01/01/70 00:00 | |
| more | 01/01/70 00:00 | |
| good idea with the EI0 | 01/01/70 00:00 | |
| no and yes | 01/01/70 00:00 | |
| why not for rapid prototyping? | 01/01/70 00:00 | |
| how would you prototype something that | 01/01/70 00:00 | |
| I agree | 01/01/70 00:00 | |
| the smarter monitors work like this | 01/01/70 00:00 | |
| not quite as smart | 01/01/70 00:00 | |
| yep | 01/01/70 00:00 | |
SBC monitor? | 01/01/70 00:00 | |
| do you want a REAL challenge? | 01/01/70 00:00 | |
| It's enough of a challenge | 01/01/70 00:00 | |
| I agree | 01/01/70 00:00 | |
| monitors ... have a look here ... | 01/01/70 00:00 | |
| cheers | 01/01/70 00:00 |