Mattias,
This is how you can fix that annoying bug with Build All asking to reset the debugger then aborting. When you do a Build All
you will get:
ConfirmationDo you want to rebuild lazarus with profile: Build All[yes] [no] Selecting yes gives
Some message that I cannot find about the debugger needs to be reset. Please change your code so that
if DebugProcessRunning then Reset;BuildAll;
I cannot find this in your code and obviously you know your way around the code better than I. Regards, PEWPeter Eric Williams
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20101226/2dfecae8/attachment.html>
Mailing lists / lazarus / 2010-12
This is how you can fix that annoying bug with Build All asking to reset the debugger then aborting.
7 messages · 5 people · –
- Juha Manninen 2
- Peter Williams 2
- Martin 1
- Peter E Williams 1
- Sven Barth 1
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Peter Williams kirjoitti sunnuntai 26 joulukuu 2010 05:14:20:
Show quoted text 11 lines
Mattias,
This is how you can fix that annoying bug with Build All asking to reset
the debugger then aborting. When you do a Build All
you will get:
ConfirmationDo you want to rebuild lazarus with profile: Build All[yes]
[no] Selecting yes gives
Some message that I cannot find about the debugger needs to be reset.
Please change your code so that
if DebugProcessRunning then Reset;BuildAll;
I cannot find this in your code and obviously you know your way around the
code better than I. Regards, PEWPeter Eric Williams
You should make a bug report with steps to reproduce. In my opinion it is ok to have a confirmation while debugging and then clicking "Build All".
Regards
Juha
Juha Manninen wrote 18 lines
Peter Williams kirjoitti sunnuntai 26 joulukuu 2010 05:14:20:
> Mattias,
> This is how you can fix that annoying bug with Build All asking to reset
> the debugger then aborting. When you do a Build All
> you will get:
> ConfirmationDo you want to rebuild lazarus with profile: Build All[yes]
> [no] Selecting yes gives
> Some message that I cannot find about the debugger needs to be reset.
> Please change your code so that
> if DebugProcessRunning then Reset;BuildAll;
> I cannot find this in your code and obviously you know your way around the
> code better than I. Regards, PEWPeter Eric Williams
>
You should make a bug report with steps to reproduce.
In my opinion it is ok to have a confirmation while debugging and then clicking
"Build All".
Until very recently it was impossible to stop or reset the debugger, in order to build anything (build \lazarus, or build a project)
Calling Debugger.Stop only scheduled a signal, and that would only be processed after the current event did finish. So it was needed to exit the current Menu.OnClick handler, or the debugger would not stop.
This has partly been solved, in most cases the debugger can now be stopped. But not always.
Technical background:
While debugging, all other code runs in a ProcessMessages called from the debugger.
Only if this returns thye debugger react's to any commands received (they are all queued).
Doing
Debugger.Stop
App.ProcessMessages
does *not* help either.
Martin
Peter Williams kirjoitti sunnuntai 26 joulukuu 2010 05:14:20: You should make a bug…
Juha,
see comments below
Fond Regards, Peter Eric WILLIAMS
--- Hobart, Tasmania, Australia
--- Phone: +61 (03) 6236-9675
My free websites are: http://pewink.info (&)
http://pewslinuxvault.googlepages.com
Juha Manninen wrote 20 lines
Peter Williams kirjoitti sunnuntai 26 joulukuu 2010 05:14:20:
> Mattias,
> This is how you can fix that annoying bug with Build All asking to reset
> the debugger then aborting. When you do a Build All
> you will get:
> ConfirmationDo you want to rebuild lazarus with profile: Build All[yes]
> [no] Selecting yes gives
> Some message that I cannot find about the debugger needs to be reset.
> Please change your code so that
> if DebugProcessRunning then Reset;BuildAll;
> I cannot find this in your code and obviously you know your way around
the
> code better than I. Regards, PEWPeter Eric Williams
You should make a bug report with steps to reproduce.
In my opinion it is ok to have a confirmation while debugging and then
clicking
"Build All".
I am currently unable to install the latest snapshot of Lazarus 0.9,31,x
--- as of 2 days ago I got as far as uncompressing all the Lazarus .deb files (for Linux) and I do not know the command to enter to install all the deb files. I am still a bit of a linux newbie in this regard :(
What is the linux terminal command to install the lazarus latest snapshot from all the deb files? Assuming that they are all in:
Home\Downloads\Lazarus <<< (contains all the .deb files)
Once you tell me the command I will investigate this bug further and report it if I think it is required.
Are the Lazarus.lpi, Lazarus.lpr and Lazarus.lfm files included in the latest snapshot ?
I would suggest that they need to be in the Lazarus root folder.
Show quoted text 9 lines
Regards
Juha
--
_______________________________________________
Lazarus mailing list
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20101229/40b95493/attachment.html>
Peter E Williams kirjoitti tiistai 28 joulukuu 2010 21:24:43:
Show quoted text 8 lines
--- as of 2 days ago I got as far as uncompressing all the Lazarus .deb
files (for Linux) and I do not know the command to enter to install all the
deb files. I am still a bit of a linux newbie in this regard :(
What is the linux terminal command to install the lazarus latest snapshot
from all the deb files? Assuming that they are all in:
Home\Downloads\Lazarus <<< (contains all the .deb files)
Forget the snapshots and use SVN instead.
Juha
Until very recently it was impossible to stop or reset the debugger, in order to build…
Hi Juha,
Show quoted text 34 lines
Date: Sun, 26 Dec 2010 13:42:29 +0100
From:
To:
Subject: Re: [Lazarus] This is how you can fix that annoying bug with Build All asking to reset the debugger then aborting.
On 26/12/2010 13:28, Juha Manninen wrote:
> Peter Williams kirjoitti sunnuntai 26 joulukuu 2010 05:14:20:
>
>> Mattias,
>> This is how you can fix that annoying bug with Build All asking to reset
>> the debugger then aborting. When you do a Build All
>> you will get:
>> ConfirmationDo you want to rebuild lazarus with profile: Build All[yes]
>> [no] Selecting yes gives
>> Some message that I cannot find about the debugger needs to be reset.
>> Please change your code so that
>> if DebugProcessRunning then Reset;BuildAll;
>> I cannot find this in your code and obviously you know your way around the
>> code better than I. Regards, PEWPeter Eric Williams
>>
> You should make a bug report with steps to reproduce.
> In my opinion it is ok to have a confirmation while debugging and then clicking
> "Build All".
>
Until very recently it was impossible to stop or reset the debugger, in
order to build anything (build \lazarus, or build a project)
Calling Debugger.Stop only scheduled a signal, and that would only be
processed after the current event did finish. So it was needed to exit
the current Menu.OnClick handler, or the debugger would not stop.
This has partly been solved, in most cases the debugger can now be
stopped. But not always.
I looked at the Windows code about 4-5 days ago.
Show quoted text 10 lines
Technical background:
While debugging, all other code runs in a ProcessMessages called from
the debugger.
Only if this returns thye debugger react's to any commands received
(they are all queued).
Doing
Debugger.Stop
App.ProcessMessages
does *not* help either.
I suggest calling Debugger.Reset
maybe also a App.ProcessMessages but I am ignorant about how this works.
Martin
PEW
Show quoted text 5 lines
--
_______________________________________________
Lazarus mailing list
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20101230/b814587a/attachment.html>
On 29.12.2010 19:53, Peter Williams wrote in a big font:
Show quoted text 5 lines
I suggest calling Debugger.Reset
maybe also a App.ProcessMessages but I am ignorant about how this works.
I'm not a list moderator, but would you please stop to change the font size to something big, because that looks like you're "yelling".
Better yet: use text only e-mails (set the format to text only in your mail client).
Regards
Sven