[Lazarus] call stack

Martin Frb lazarus at mfriebe.de
Thu Jun 18 14:32:02 CEST 2020

On 18/06/2020 10:52, Евгений Кадисов via lazarus wrote:
> Hi everybody.
> In what cases can be such a situation. The call stack is full of 
> strange stuff and does not contain any string of the debugged code.

Make sure to open the threads window, and set each thread to current. 
Even if your app does not have threads, there may be some.

How did your app stop/pause?

Did you single step?
Did you hit the pause button?
Did the app report an error?

The pause button:
Unless your app is 100% busy (form does not respond), the pause button 
will probably pause your app in the kernel.
Otherwise it may be in the wrong thread.

App reported Error.
This can be in a library. Sometimes libraries produces stacks that can 
not be read by the debugger. But also make sure you show more than 10 
frame, if available.
Or this can be a SigSegV, which can (one of many reasons) be due to a 
corrupt stack. In that case there is no stack no more. (Make sure you 
compile with range checking)

More information about the lazarus mailing list