The info is enough for explaining what happens.
Before I go to the reason: It is strange the debugger does not indicate
that your app was killed by a signal SigTrap. (That should be reported
as bug)
The signal is actually caused by FPC (more below), and it looks like
this causes windows to
Oh, View menu, of course. I am stupid indeed. :)
I just updated a GDB to version 7.7.1 and now at least the stack trace
makes more sense. It is full of Windows API calls. However, here is a
part of debug output which seems to be relevant, at least I am not sure
what exactly this can be:
On 13/11/17 16:26, Martin Frb via Lazarus wrote:
Some more info on the original questions:
While it would still be good to know what happens (see other part of
this mail thread.)
If this is caused by a 3rd party library, you may try if the following helps
go to menu Tools, options.
On the
Some more info on the original questions:
The error about "not finding boundary", happens because your app is
paused in code with no debug info. So the debugger does not know where
the function starts or end. Nor does it know where the line starts, as
there is no info on lines.
Alt F7 will
On 13/11/17 10:40, Lubos Pintes via Lazarus wrote:
What that means? An exception, access violation or what?
It probably happens somewhere in my UI Automation implementation. The
Call stack window doesn't show useful information.
An F7 key tells something like "Cannot find function boundary".
What that means? An exception, access violation or what?
It probably happens somewhere in my UI Automation implementation. The
Call stack window doesn't show useful information.
An F7 key tells something like "Cannot find function boundary".
So curently I don't know how to debug this problem.
