Hi,

My env is:
Lazarus 0.9.31 r31914 FPC 2.4.5 i386-win32-win32/win64

After a Build all, the IDE does not restart.
The compilation is Ok; IDE was closed; show the splash again... but the IDE is gone.

Any tips?

Marcos Douglas

1. To get the old IDE:
Normally the IDE renames the old executable to lazarus.old.exe under Windows (or something like that).

2. Always keep backups.

3. To debug, why the installed package makes problems: Start the lazarus.exe with command line parameter --debug-log=log.txt or debug the IDE with the IDE.

Mattias

I think did you not understand.
The lazarus.exe and lazarus.old.exe continues existing but the startlazarus did not can restart it after a Build all.

2. Always keep backups.

I always have.

3. To debug, why the installed package makes problems: Start the lazarus.exe with command line parameter --debug-log=log.txt or debug the IDE with the IDE.

Ok, I will try that.

Marcos Douglas

When I use the --debug-log startlazarus.exe and lazarus.exe stay in Windows Task Manager but nothing happen.

The last lines of log are below:
[...]
Compiling restrictionbrowser.pas
Compiling projectwizarddlg.pas
Compiling resource ..\units\i386-win32\lazarus.or
Linking W:\md\dev\freepascal\ide\laz\0.9.31\lazarus.new.exe 258093 lines compiled, 275.3 sec , 9042752 bytes code, 5267128 bytes data 5 warning(s) issued
make.exe[2]: Leaving directory `W:/md/dev/freepascal/ide/laz/0.9.31/ide' make.exe[1]: Leaving directory `W:/md/dev/freepascal/ide/laz/0.9.31/ide' W:\md\dev\freepascal\binutils\2.4.5\i386-win32\make.exe: Leaving directory `W:/md/dev/freepascal/ide/laz/0.9.31'
"IDE" completed
TMainIDE.DoRestart SetPrimaryConfigPath
NewValue="W:\md\dev\freepascal\ide\laz\0.9.31-config" -> "W:\md\dev\freepascal\ide\laz\0.9.31-config"
Adding "--pcp=W:\md\dev\freepascal\ide\laz\0.9.31-config" as a parameter Adding "--lazarus-dir=W:\md\dev\freepascal\ide\laz\0.9.31" as a parameter Adding "--debug-log=c:\lazlog.txt" as a parameter
LAZARUS END - cleaning up ...
\laz\0.9.31-config"
Adding "--pcp=W:\md\dev\freepascal\ide\laz\0.9.31-config" as a parameter Adding "--lazarus-dir=W:\md\dev\freepascal\ide\laz\0.9.31"[FORMS.PP] ExceptionOccurred
Sender=EInOutError
Exception=Access denied
Stack trace:
$00C52FCE STARTLOG, line 454 of src/daemonapp.pp TApplication.HandleException Access denied
Stack trace:
$00C52FCE STARTLOG, line 454 of src/daemon

---

Marcos Douglas

Both binaries are frozen... using or not --debug-log parameter.

Marcos Douglas

This problem do not occurs with Lazarus 0.9.30.1.
(Lazarus 0.9.30.1 r31020 FPC 2.4.5 i386-win32-win32/win64)

See the diff:
[...]
Compiling restrictionbrowser.pas
Compiling projectwizarddlg.pas

Compiling resource ..\units\i386-win32\lazarus.or
Linking W:\md\dev\freepascal\ide\laz\0.9.30\lazarus.new.exe 189650 lines compiled, 333.1 sec , 9280640 bytes code, 5274044 bytes data 5 warning(s) issued
2 note(s) issued
make.exe[2]: Leaving directory `W:/md/dev/freepascal/ide/laz/0.9.30/ide' make.exe[1]: Leaving directory `W:/md/dev/freepascal/ide/laz/0.9.30/ide' W:\md\dev\freepascal\binutils\2.5.1\i386-win32\make.exe: Leaving directory `W:/md/dev/freepascal/ide/laz/0.9.30'
"IDE" completed
TMainIDE.DoRestart SetPrimaryConfigPath
NewValue="W:\md\dev\freepascal\ide\laz\0.9.30-config" -> "W:\md\dev\freepascal\ide\laz\0.9.30-config"
Adding "--pcp=W:\md\dev\freepascal\ide\laz\0.9.30-config" as a parameter Adding "--lazarus-dir=W:\md\dev\freepascal\ide\laz\0.9.30" as a parameter Adding "--debug-log=c:\lazlog-30.txt" as a parameter LAZARUS END - cleaning up ...
-config"
Adding "--pcp=W:\md\dev\freepascal\ide\laz\0.9.30-config" as a parameter Adding "--lazarus-dir=W:\md\dev\freepascal\ide\laz\0.9.30" as a parameter Adding "--debug-log=c:\lazlog-30.txt" as a parameter TLazarusManager.Run DefaultDir="W:\md\dev\freepascal\ide\laz\0.9.30\" CustomDir="W:\md\dev\freepascal\ide\laz\0.9.30-config\bin\" TLazarusManager.Run starting W:\md\dev\freepascal\ide\laz\0.9.30\lazarus.exe ... ICATE RESOURCE FOUND: TPRImage:XPM
SetPrimaryConfigPath
NewValue="W:\md\dev\freepascal\ide\laz\0.9.30-config" -> "W:\md\dev\freepascal\ide\laz\0.9.30-config"
TLResourceList.Sort 498 DUPLICATE RESOURCE FOUND: TPRImage:XPM TLResourceList.Sort 501 DUPLICATE RESOURCE FOUND: TPRImage:XPM TFPCTargetConfigCache.NeedsUpdate compiler file changed "W:\md\dev\freepascal\compiler\2.4.5\bin\i386-win32\fpc.exe" FileAge=1058638343
StoredAge=1057196718TFPCTargetConfigCache.[[[[...SNIP...]]]].Update: has changedLAZARUS END - cleaning up ...

Marcos Douglas

I suppose this is not related to the problem reported, at least I assumed "the IDE is gone" as having no trace of its process in the TaskManager.

But I "always" see this :-/ At In my case the problem is if you start Lazarus by itself (without using StartLazarus), when the IDE is (first) restarted, StartLazarus is launched before the MemCheck output is shown, so its MessageBox is behind the splashscreen. In Win7, though, the "Error" window button is show in the taskbar I can just close it using the menu.
It's seems easy to fix, but I didn't come to conclusion what's the best fix.

Doh! I've just realized what a donkey I am: simply changing the Lazarus shortcut to point to StartLazarus instead fixes this, and fixes the --no-splash-screen not being respected. It has the disadvantage of not "grouping" the running instance with the shortcut/launching button, though... (and I'd really prefer not having startlazarus running all time - I suppose it has no tasks while waiting? - but checking now it's only 3MB RSS, I remember having seen 20MB before...)

-Fl?vio

I had this problem, caused by (memcheck...) dialogs hidden behind the splash screen. Start with --no_splash_screen (or the like), or remove the splash screen display from the lpr.

DoDi

Hm... Ok, I will try this before the next build. Thanks.

Marcos Douglas

2011/9/14 Fl?vio Etrusco :

Both happend: the IDE gone (no trace in TaskManager) and the IDE lock.

Hm... I do not use startlazarus too - I used, but seeing my BAT script now it uses lazarus.exe (I must have changed it for some time and did not remember).
I will try, thanks.

Marcos Douglas

You were right. Using startlazarus this problem not happend. But, in Lazarus 0.9.30.1 this problem not occurs even using lazarus.exe instead of startlazarus.exe.

Marcos Douglas