Hello,
I have some problems for setting breakpoints in my assembly langage sources directly (double clic) When i set them (double clic) in edition mode, the red square appears in the left column but when i pass in debug mode, this red square has disappeared. In the beakpoint windows (ctrl+B)i can verify that the breakpoint is still present and when i run the program it is effective. However it is impossible to visualize it in my source windows and to set a new breakpoint with the mouse (without passing back to edition mode...). Another strange behavior is that the breakpoints can be directly set in the desassembly windows...
A priori there is no problem with sources in C. I use the last version of keil (4.23)
Thank's for any help
V.M
My sources are written in assembly language...it is why i distinguish source window et desassembly window.
For your problem it is probably due to 'optimization option' of the C compilier Try to witch off any optimization (configuration of the target) V.M
For your problem it is probably due to 'optimization option' of the C compilier Try to witch off any optimization (configuration of the target) That the result of a computation within an if does not show has absolutotally nothing to do with optimization.
Erik
ok you are right. ...sorry i have read too quickly your post.... you can't effectively not see the result of your soustraction because you haven't any affectation for this operation.
and for my problem, no idea? V.M
... does not show the issue you have. Breakpoints are red and stay red.
I do not recall the occasion or the problem, but at one time, long ago, with some problem (see below) the solution was to add one C module to an otherwise assembler only program:
void main(void) { run_assembler_code(); }
I have no idea if that will help you
It was long ago, in the days when a higher percentage was assembler, but if I recall it was something like that you can not breakpoint in a c module if you do not have a c main or some such thing.