SX Key IDE behaviours
Michael Chadwick
Posts: 80
Hi All, but probably mostly Peter Montgomery.
I haven't posted since the forum moved, but we were having a little discussion about the IDE behaviour under WinXP.· I just wanted to recap, since a quick look at the forum didn't seem to cover any of the issues in substance.
So to recap:
The programming progress window gets 'stuck' i.e. never goes away if you switch focus to another window while programming to run or debug.· This doesn't seem to actually cause a problem with programming, just the window never goes away, and sometimes doesn't update to indicate programming was completed.· This only seems to happen under WinXP, judging from other posts.
The SX program being debugged will sometimes head off into unused code space, usually up high, like 784h in the instance I just saw.· Double clicking in the source code at the last proper·instruction in order to reset the program counter seems to get around it and allow continued debugging, you just have to be vigilant to catch it when it happens.· This sort of thing has happened to me since I bought my first SX key, about 4 years ago. So not likely to be an IDE problem.
I have had occasions where pressing CTRL-ALT-D wouldn't re-enter debugging, but that problem seems to have gone away.
There are occasionally cases where SASM crashes out, which seem to be related to nested IFDEFs I think.
Other than that it is a great tool!!!!!!
Thanks
Mike Chadwick
I haven't posted since the forum moved, but we were having a little discussion about the IDE behaviour under WinXP.· I just wanted to recap, since a quick look at the forum didn't seem to cover any of the issues in substance.
So to recap:
The programming progress window gets 'stuck' i.e. never goes away if you switch focus to another window while programming to run or debug.· This doesn't seem to actually cause a problem with programming, just the window never goes away, and sometimes doesn't update to indicate programming was completed.· This only seems to happen under WinXP, judging from other posts.
The SX program being debugged will sometimes head off into unused code space, usually up high, like 784h in the instance I just saw.· Double clicking in the source code at the last proper·instruction in order to reset the program counter seems to get around it and allow continued debugging, you just have to be vigilant to catch it when it happens.· This sort of thing has happened to me since I bought my first SX key, about 4 years ago. So not likely to be an IDE problem.
I have had occasions where pressing CTRL-ALT-D wouldn't re-enter debugging, but that problem seems to have gone away.
There are occasionally cases where SASM crashes out, which seem to be related to nested IFDEFs I think.
Other than that it is a great tool!!!!!!
Thanks
Mike Chadwick
Comments
A good summary. One question I had related to SASM crashing. Do you have any code that displays this behavior consistently? You mentioned nested Ifdef's, being a possible culprit. I'd love to see any code that causes problems so I can try and make SASM return an error instead of crashing.
Thanks, PeterM
As I was mostly interested in getting my code to compile, I didn't take time to save the pathological case.· I'll see if I can reproduce it this week and post it.
One thing I forgot to mention in the list is the following behaviour, if you have a breakpoint set, all the buttons except reset are greyed out.· Is this out of necessity because of the way the sx handles debugging?· It would be nice if one could just do a STOP if the program never hits the breakpoint.
Thanks
Mike Chadwick