[Lazarus] This is how you can fix that annoying bug with Build All asking to reset the debugger then aborting.

[Peter Williams]

Hi Juha,

> Date: Sun, 26 Dec 2010 13:42:29 +0100
> From: lazarus at mfriebe.de
> To: lazarus at lists.lazarus.freepascal.org
> 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.

> 
> 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

> --
> _______________________________________________
> Lazarus mailing list
> Lazarus at lists.lazarus.freepascal.org
> http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20101230/b814587a/attachment-0003.html>