On 29/11/2019 22:26, Bo Berglund via lazarus wrote:
Well, my code does not really get involved in this because it is just
a bunch of text files the IDE is showing for editing, right?
Because the crash happens when I am editing and typically when I click
on something in the editor window.
But the
On Fri, 29 Nov 2019 18:11:12 +0100, Martin Frb via lazarus
wrote:
>The only odd part is, that if there was such a writeln, I would expect a
>lot more people having problems But one never knows. Maybe something
>particular in your code causes this "write". Or a package added to the
>IDE
On 29/11/2019 17:27, Bo Berglund via lazarus wrote:
I also wonder exactly what you meant for me to do above concerning the
debug-log?
Do you mean for me to use that command inside gdb to start lazarus?
In that case I also need to set the --pcp option, right?
Or did you mean it as an alternative
On Thu, 28 Nov 2019 15:14:47 +0100, Martin Frb via lazarus
wrote:
>On 28/11/2019 15:10, Martin Frb via lazarus wrote:
>>
>> You could try running lazarus, without gdb, but with output
>> redirection to a file.
>> Lazarus has some logging that checks for an open console. So there
>> will be cont
IMHO, in the end it should be possible to do an application in an RAD-way (if
desired), test it on a desktop (using the desktop Widgets for its GUI), scale
it (by defining parts of the procedures as "Remote"), and finally (just by
re-compiling) have it run as a combination of application-parts
