Re: [Lazarus] rc2 debugger error
Hi Martin, Thank you for the instructions! That is very cool (-gw), didn't know how to do that...I will be playing there sometimes methinks... Anyway, I followed instructions and there are no call stack messages, the debugger error window shows up immediately. I put a breakpoint in formcreate and also in the project source both, in the hope it would force something, but unfortunately neither breakpoint was hit. Am archiving the original problematic PUB files and will send to you. BTW, any drawbacks to keeping the -gw switch on? I'd like to keep the ability to debug ide I guess,...just in case ;-) Julius On 03/04/2015 03:14 PM, Martin Frb wrote: On 04/03/2015 13:37, JuuS wrote: Hi all, FYI, all the issues are exactly the same with rc2 as it was with rc1 as regards opening and running a published version of my project vs. the original/unchanged project. Solution is once again removing default icon entry in LPI file. Has no one else seen this? If you want I have no problem sending the published folder (it's not big) to someone who may want to trace it in some manner. You can sent it. With luck it will reproduce. It might be something that depends on the exact OS version/ setup you have. Also you could try this: Debug the IDE when it happens. - Start Lazarus, as you always to. - Tools configure build lazarus = rebuild with -gw in the options - restart - open project ide/lazarus.lpi - F9 Now a 2nd Lazarus starts. In this 2nd Lazarus open your published project, and try to run it. Hopefully it produces the error. With a bit of luck the first started IDE will report that there was an exception. Get a stacktrace. Thanks -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] rc2 debugger error
On 04/03/2015 17:58, JuuS wrote: Hi Martin, Thank you for the instructions! That is very cool (-gw), didn't know how to do that...I will be playing there sometimes methinks... Anyway, I followed instructions and there are no call stack messages, the debugger error window shows up immediately. Try setting a breakpoint in ide\debugmanager.pas procedure TDebugManager.DebuggerChangeState(ADebugger: TDebuggerIntf; OldState: TDBGState); line 1150 if FDebugger.State=dsError then begin Include(FManagerStates,dmsDebuggerObjectBroken); if dmsInitializingDebuggerObject in FManagerStates then Include(FManagerStates,dmsInitializingDebuggerObjectFailed); end; inside the if. That should do. Another test you could do: Do not use F9 (Run), which builds, and runs. Instead go to the menu, and choose build. Then when the build finished, press run (F9 or menu) Am archiving the original problematic PUB files and will send to you. Thanks got them. Unfortunately it does not happen on my system. (Tried Windows and linux) BTW, any drawbacks to keeping the -gw switch on? I'd like to keep the ability to debug ide I guess,...just in case ;-) Only the size of the lazarus.exe. I usually build with -gh -g -gw -godwarfsets -Criot -gtt -Sa -O1 -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] rc2 debugger error
Thanks Martin, Will do...tomorrow Will send (any?!) results to you... Guten Abend, Julius On 03/04/2015 07:25 PM, Martin Frb wrote: On 04/03/2015 17:58, JuuS wrote: Hi Martin, Thank you for the instructions! That is very cool (-gw), didn't know how to do that...I will be playing there sometimes methinks... Anyway, I followed instructions and there are no call stack messages, the debugger error window shows up immediately. Try setting a breakpoint in ide\debugmanager.pas procedure TDebugManager.DebuggerChangeState(ADebugger: TDebuggerIntf; OldState: TDBGState); line 1150 if FDebugger.State=dsError then begin Include(FManagerStates,dmsDebuggerObjectBroken); if dmsInitializingDebuggerObject in FManagerStates then Include(FManagerStates,dmsInitializingDebuggerObjectFailed); end; inside the if. That should do. Another test you could do: Do not use F9 (Run), which builds, and runs. Instead go to the menu, and choose build. Then when the build finished, press run (F9 or menu) Am archiving the original problematic PUB files and will send to you. Thanks got them. Unfortunately it does not happen on my system. (Tried Windows and linux) BTW, any drawbacks to keeping the -gw switch on? I'd like to keep the ability to debug ide I guess,...just in case ;-) Only the size of the lazarus.exe. I usually build with -gh -g -gw -godwarfsets -Criot -gtt -Sa -O1 -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] rc2 debugger error
On Wed, Mar 4, 2015 at 3:37 PM, JuuS j...@mykolab.ch wrote: but you may remember that ... How should we remember? Did you report those problems earlier somewhere? Is it a regression in 1.4 compared to 1.2? Maybe you should open a ticket with an example project and steps to reproduce. Juha -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
Re: [Lazarus] rc2 debugger error
On 04/03/2015 13:37, JuuS wrote: Hi all, FYI, all the issues are exactly the same with rc2 as it was with rc1 as regards opening and running a published version of my project vs. the original/unchanged project. Solution is once again removing default icon entry in LPI file. Has no one else seen this? If you want I have no problem sending the published folder (it's not big) to someone who may want to trace it in some manner. You can sent it. With luck it will reproduce. It might be something that depends on the exact OS version/ setup you have. Also you could try this: Debug the IDE when it happens. - Start Lazarus, as you always to. - Tools configure build lazarus = rebuild with -gw in the options - restart - open project ide/lazarus.lpi - F9 Now a 2nd Lazarus starts. In this 2nd Lazarus open your published project, and try to run it. Hopefully it produces the error. With a bit of luck the first started IDE will report that there was an exception. Get a stacktrace. Thanks -- ___ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
