I've just detected, that the software-debugger needs to be restarted after a change in the source-code has occured. It is not sufficient just to build the new code.
While this behaviour is usual for any hardware-debugger (the new source has to be programmed to the target-processor), it is pretty uncomfortable for the handling of the software-debugger (= simulator). Maybe it is possible to change this?
Thanks,
Stefan
Strange behaviour of software-debugger
Hi Stefan, see also http://www.mikroe.com/forum/viewtopic.php?t=19088.
Kind regards, Dany.
Forget your perfect offering. There is a crack in everything, that's how the light gets in... (L. Cohen)
Remember when we were young? We shone like the sun. (David Gilmour)
Forget your perfect offering. There is a crack in everything, that's how the light gets in... (L. Cohen)
Remember when we were young? We shone like the sun. (David Gilmour)
-
Stefan Uhlemayr
- Posts: 158
- Joined: 17 Jan 2009 21:33
Looks like I've missed something... Unfortunately, it is not solved in v1.40.Dany wrote:Hi Stefan, see also http://www.mikroe.com/forum/viewtopic.php?t=19088.
Thanks,
Stefan
-
Stefan Uhlemayr
- Posts: 158
- Joined: 17 Jan 2009 21:33
Rebuilding the project is not sufficient (when software-debugger is running already), you have to restart the debugger, that it will understand the changes - and this need for restarting is not very comfortable. By the way, saving the project is grayed out, when I simply change the code, but the files are saved automatically before they are build.zristic wrote:After you modify the code, you have to save it and to rebuild the project in order for the debugger to understand changes.
