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
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
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
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 content in that file, that does not confirm anything about a
rogue writeln. But if
On 28/11/2019 12:08, Bo Berglund via lazarus wrote:
On Mon, 25 Nov 2019 10:31:51 +0100, Bo Berglund via lazarus
wrote:
OK, This worked!
Now I have a Lazarus IDE running after starting via gdb.
Lets see how long it will take before the next crash...
So it has been running fine now for 72
On Thu, 28 Nov 2019 12:08:30 +0100
Bo Berglund via lazarus wrote:
> On Mon, 25 Nov 2019 10:31:51 +0100, Bo Berglund via lazarus
> wrote:
>
> >OK, This worked!
> >Now I have a Lazarus IDE running after starting via gdb.
> >Lets see how long it will take before the next crash...
>
> So it has
On Mon, 25 Nov 2019 10:31:51 +0100, Bo Berglund via lazarus
wrote:
>OK, This worked!
>Now I have a Lazarus IDE running after starting via gdb.
>Lets see how long it will take before the next crash...
So it has been running fine now for 72 hours while I have coded a lot.
No crashes that plagued
On Sun, 24 Nov 2019 20:52:49 +0100, Martin Frb via lazarus
wrote:
>In the terminal enter
>
>gdb /home/pi/dev/lazarus/2.0.6/lazarus
>
>
>then wait for the gdb output. It will end with a "(gdb)" prompt.
>Now enter
>
>r --pcp=/home/pi/.lazarus_2.0.6
>
OK, This worked!
Now I have a Lazarus IDE
On 24/11/2019 20:42, Bo Berglund via lazarus wrote:
After reading the gdb --help screen:
pi@rpi4-gui:~ $ gdb --args /home/pi/dev/lazarus/2.0.6/lazarus
No --args
In the terminal enter
gdb /home/pi/dev/lazarus/2.0.6/lazarus
then wait for the gdb output. It will end with a "(gdb)" prompt.
On Sun, 24 Nov 2019 18:27:40 +0100, Bo Berglund via lazarus
>I tried but
>pi@rpi4-gui:~ $ gdb /home/pi/dev/lazarus/2.0.6/lazarus r
>--pcp=/home/pi/.lazarus_2.0.6
>gdb: unrecognized option '--pcp=/home/pi/.lazarus_2.0.6'
>Use `gdb --help' for a complete list of options.
>
>So now the --pcp...
On 24/11/2019 18:27, Bo Berglund via lazarus wrote:
On Sun, 24 Nov 2019 14:46:11 +0100, Martin Frb via lazarus
wrote:
On 24/11/2019 10:22, Bo Berglund via lazarus wrote:
On Sun, 24 Nov 2019 03:21:11 +0100, Martin Frb via lazarus
wrote:
If you can Run your Lazarus in gdb.
gdb
On Sun, 24 Nov 2019 14:46:11 +0100, Martin Frb via lazarus
wrote:
>On 24/11/2019 10:22, Bo Berglund via lazarus wrote:
>> On Sun, 24 Nov 2019 03:21:11 +0100, Martin Frb via lazarus
>> wrote:
>>> If you can Run your Lazarus in gdb.
>>> gdb path/to/lazarus
>>>
>>> and then in gdb hit r
On 24/11/2019 10:22, Bo Berglund via lazarus wrote:
Exec=/home/pi/dev/lazarus/2.0.6/startlazarus
--pcp=/home/pi/.lazarus_2.0.6 %f
Off topic, if you use this as a single user system, you can put the pcp
into a file called lazarus.cfg
On 24/11/2019 10:22, Bo Berglund via lazarus wrote:
On Sun, 24 Nov 2019 03:21:11 +0100, Martin Frb via lazarus
wrote:
If you can Run your Lazarus in gdb.
gdb path/to/lazarus
and then in gdb hit r and return.
I can use different versions on the same system. So the command to
start
El 24/11/19 a les 10:22, Bo Berglund via lazarus ha escrit:
On Sun, 24 Nov 2019 03:21:11 +0100, Martin Frb via lazarus
wrote:
On 24/11/2019 01:30, Bo Berglund via lazarus wrote:
And I have been bitten several times the last days by the suddenly
disappearing Lazarus application
If you
On Sun, 24 Nov 2019 03:21:11 +0100, Martin Frb via lazarus
wrote:
>On 24/11/2019 01:30, Bo Berglund via lazarus wrote:
>> And I have been bitten several times the last days by the suddenly
>> disappearing Lazarus application
>
>If you can Run your Lazarus in gdb.
> gdb path/to/lazarus
On 24/11/2019 01:30, Bo Berglund via lazarus wrote:
And I have been bitten several times the last days by the suddenly
disappearing Lazarus application
If you can Run your Lazarus in gdb.
gdb path/to/lazarus
and then in gdb hit r and return.
I know you want to get away from more
On Sat, 2 Nov 2019 15:37:23 +0100, Martin Frb via lazarus
wrote:
>On 02/11/2019 14:48, Bo Berglund via lazarus wrote:
>>
>> Now it happened again!
>> I was compiling the program then executing it inside a terminal
>> (external to Lazarus) and then repeating this to find my bug.
>>
>> When I
On 02/11/2019 14:48, Bo Berglund via lazarus wrote:
Now it happened again!
I was compiling the program then executing it inside a terminal
(external to Lazarus) and then repeating this to find my bug.
When I found it I doubleclicked the name of my logging component to
copy its name, but
On Fri, 1 Nov 2019 23:03:16 +0100, Martin Frb via lazarus
wrote:
>> I have never before encountered a crash like this, could it be because
>> the IDE is so "fresh out of the presses"?
>Good question "why". That can't be answered easily. And the issue could
>be new or old.
>
>Unfortunately more
On Sat, 2 Nov 2019 06:00:44 +0100, Ondrej Pokorny via lazarus
wrote:
>On 01.11.2019 23:03, Martin Frb via lazarus wrote:
>> Well and a "autosave" feature might be nice, but needs to be written...
>
>The project is always automatically saved when you compile it.
>
Yes, I know that and it works
On 01.11.2019 23:03, Martin Frb via lazarus wrote:
Well and a "autosave" feature might be nice, but needs to be written...
The project is always automatically saved when you compile it.
Ondrej
--
___
lazarus mailing list
On 01/11/2019 22:10, Bo Berglund via lazarus wrote:
I installed Lazarus 2.0.6 a few hours ago into a fully updated
Raspbian Buster on an RPi4B 4GB system. Interfacing to it using
RealVNC to my Windows7 laptop.
I opened the current project and checked that it would build etc. No
problems.
Then
I installed Lazarus 2.0.6 a few hours ago into a fully updated
Raspbian Buster on an RPi4B 4GB system. Interfacing to it using
RealVNC to my Windows7 laptop.
I opened the current project and checked that it would build etc. No
problems.
Then I started write a section of description comments at
25 matches
Mail list logo
