The idea is: F8 stops only at the user app's code, not in LCL nor in other components.
In a similar way, how to avoid F8 from going to assembly part of instructions?
In a similar way, how to avoid F8 from going to assembly part of instructions?If you want to debug the compiler itself or one of the standard libraries you need no compile everything with debug information.
If you want to debug the compiler itself or one of the standard libraries you need no compile everything with debug information.In the context of the thread "stick to the users own (aka user-written) units only" (derived from the original post quote "the main unit"), and seeing no indication in jcmontherock's post that his post wasn't part of that context, how did we get to debugging - with full indent of the user - the RTL or FCL?
Then you get what you want, but for beginners or intermediates it is not that straightforward, but doable.
that the step F8 only stopped in the main unit.
Is that when you use F8 to step from one paused line to the next line?
How do we do an update of fpDebug under Windows ?
Or do you, @Thaddy, have information that he is indeed the author of any of those units? scnr.No, I am only the author of a couple of 10'ths of accepted patches and a 25% contributor to KOL. And a noise, sometimes.
Or do you, @Thaddy, have information that he is indeed the author of any of those units? scnr.No, I am only the author of a couple of 10'ths of accepted patches and a 25% contributor to KOL
Thanks a lot Martin_fr I did what you suggest. So, debugging is clearly better. I do not have a lot of assembly codes debug.Glad to hear.