It looks like I'm the only one with this trouble.Project > New Project > Run > Image related.It can't run my old projects too. I can't run anything.I've updated it from Lazarus 2.0.12.What did I do wrong?
'Change Class' not working in 2.2.0...? Whatever I choose, it just doesn't do anything - no errors, just nothing. Any setting I am missing...?
Hello,Quote from: Nicola Gorlandi on January 09, 2022, 06:11:02 pmI know, I try to replicate with a minimum amount of code but it works.I have a component inherited from TDOSComand that I found in www.torry.net.My component just call inherited in the destroy. The destroy in TDOSComand isCode: Pascal [Select][+][-]destructor TDosCommand.Destroy;begin if FThread <> nil then Stop; if FTimer <> nil then FTimer.free; if FSync <> nil then FSync.Free; if FInputLines_SHARED <> nil then FInputLines_SHARED.free; if FLines_SHARED<> nil then FLines_SHARED.free; inherited;end; unfortunately the debug do not allow me to step in the procedure (as I put a breakpoint Lazarus show it as unreachable)it seems that it is the debugger on 2.2 version of lazarus that causes the problem :no problem with version 2.0.12 when exiting a doscommand test program.no problem when exiting a doscommand test program without debug in 2.2 version of Lazarus.Access violation when exiting a doscommand test program with debug in 2.2 version of Lazarus (see attachment).Friendly, J.P
I know, I try to replicate with a minimum amount of code but it works.I have a component inherited from TDOSComand that I found in www.torry.net.My component just call inherited in the destroy. The destroy in TDOSComand isCode: Pascal [Select][+][-]destructor TDosCommand.Destroy;begin if FThread <> nil then Stop; if FTimer <> nil then FTimer.free; if FSync <> nil then FSync.Free; if FInputLines_SHARED <> nil then FInputLines_SHARED.free; if FLines_SHARED<> nil then FLines_SHARED.free; inherited;end; unfortunately the debug do not allow me to step in the procedure (as I put a breakpoint Lazarus show it as unreachable)
it seems that it is the debugger on 2.2 version of lazarus that causes the problem :no problem with version 2.0.12 when exiting a doscommand test program.no problem when exiting a doscommand test program without debug in 2.2 version of Lazarus.Access violation when exiting a doscommand test program with debug in 2.2 version of Lazarus (see attachment).
Quote from: Jurassic Pork on January 10, 2022, 01:41:03 pmit seems that it is the debugger on 2.2 version of lazarus that causes the problem :no problem with version 2.0.12 when exiting a doscommand test program.no problem when exiting a doscommand test program without debug in 2.2 version of Lazarus.Access violation when exiting a doscommand test program with debug in 2.2 version of Lazarus (see attachment).Do you have a sample that reproduces the issue (including copy of the DosCommand package you use (if that is open source / can be shared). Target 32 bit?Debugged from within a 64 or 32bit IDE ?=> If you have, then please create an issue in the bug tracker.