Seems I'm rather unlucky with debuggers
On a specific Windows 10 machine the executable cannot be debugged, when I add a specific feature.
I means, I have $IFDEFed the sections of the code that inhibit the correct startup, and reduced the code to a small subset, so I can easily try with various options available in the IDE, but I've been unable to fix the problem.
The very same project can be debugged without problems on at least 3 different win10 machines, but
where I need it most it refuses to start, displaying instead the message allegated.
I've tried to enable the system log - as suggested by Martin_fr in
https://forum.lazarus.freepascal.org/index.php/topic,50852.msg372328.html#msg372328 - but haven't found anything notable. Of course, there is the same info displayed by the error box:
...
<< TCmdLineDebugger.ReadLn "=thread-exited,id="2",group-id="i1""
<< TCmdLineDebugger.ReadLn "=thread-group-exited,id="i1""
<< TCmdLineDebugger.ReadLn "^error,msg="During startup program exited with code 0xc0000135.""
...
The application in release mode starts without problems (if launched from the IDE or the Windows shell), while in debug mode Windows doesn't run it. Seems the executable format is wrong for some reasons. The feature I switch on/off is just a recompilation of an old component (FlexCel), where - to be true - I don't know how to regenerate the EmptySheet.res that gets embedded during the build process... but the old one works - as I said - on every other machine I've tried... so should not be the problem...
I understand this is a poor question, but... is there any chance to get the debugger working on that machine ? It's a lot that I'm unable to progress on this problem.
TIA for any help...
Carlo