Delphi 11.1 + patches - No debug source / breakpoints?

[Lars Fosdal 1793]

I have the weirdest issue.  I just installed a fresh Delphi 11.1 + patches on a new, fully patched Windows 10 Enterprise laptop.

For some weird reason - I can't debug.  Breakpoints don't break.  Exceptions break shows assembly code, says it is mixed mode, but no source lines show, and I can't trace to next sourceline.

 

Yes, I am in 32-bit debug mode. 
Yes, the project has the debug settings and debug info included. 
Yes, the output folders have full access for the current user.

Yes, there is only one set of DCUs in the path.
Yes, there is only one .EXE file.
Edit:
Yes, they are debug DCUs
Yes, line endings are CRLF

Yes, current user has local admin rights

As soon as my app starts, the breakpoints are grayed out.

 

Edit 2:
It does not happen to all apps. 
The problem app is about 600k lines. 
Tiny apps and a larger 1100k line app - no problems.

 

What am I missing?

 

Update - Possible causes?
A developer on a non-corporate laptop does not have this problem.

Another developer on corporate laptops have the same problem as me on both new and old laptops.

That seems to indicate a Windows policy may be a factor here.

 

Anyways - workaround:

Project | Options | Linking | Include remote debug symbols: A tick here gave working breakpoints for us.

[Attila Kovacs 631]

4 minutes ago, Lars Fosdal said:

Yes, there is only one set of DCUs in the path.

and they are debug dcu's? (Use debug .dcus)

Edited December 15, 2022 by Attila Kovacs

[Lajos Juhász 295]

I don't know please tell us. I have had a situation when I was unable to debug a package with one exe.  Changed the application that is used for debugging (host application) then the break point worked every time. Next week I was able to debug with both applications.

 

[Lars Fosdal 1793]

1 minute ago, Attila Kovacs said:

and they are debug dcu's? (Use debug dcu)

[Attila Kovacs 631]

ok, well, I'd try clean/build or remove the .dproj and reconfigure the project.. is this the only one IDE installed on that machine?

[Lars Fosdal 1793]

Yes - clean machine - clean install - no previous Delphis - and the .dproj files came from a repository also maintained with Delphi 11.1.

[Fr0sT.Brutal 900]

Test project - the same?

[Lars Fosdal 1793]

3 minutes ago, Fr0sT.Brutal said:

Test project - the same?

Yes - started a new project. Same problem.

No! I closed all projects, then tried again with a brand new project. 
That worked.

 

[Attila Kovacs 631]

 

Edited December 15, 2022 by Attila Kovacs

[Attila Kovacs 631]

Last one, did you restart your PC after installing the IDE? 🙂 

[Lars Fosdal 1793]

Deleting the .dproj did solve the problem. I compared the newly created to the old one, and there was a huge amount of crap in the old one.  But, why does it work on the old installation?

[PeaShooter_OMO 11]

The old one had the Crap-O-Reader installed

 

Sorry, I could not help myself

[Lars Fosdal 1793]

The plot thickens: 

I deleted the .dproj for a specific app.  Debugging worked.

I opened a project group- containing the same app.  Debugging stopped working.

Guess I need to rebuild that too.

 

Strike that. I ran the wrong project ><

[Lars Fosdal 1793]

The downside of deleting the .dproj file.

Output path, search path, dcu output path, and EurekaLog needs to be reconfigured.  Oh, such joy.

[Lars Fosdal 1793]

Another app, same problem - except this time, deleting the .dproj did not solve the problem.

WTF is going on?

[programmerdelphi2k 237]

2 hours ago, Lars Fosdal said:

and there was a huge amount of crap in the old one.

Any changes to validate file contents? If you found garbage in the ".DPROJ", then other files could be contaminated as well....

Was there any strange situation when copying the files?

 

Just lingering on about possible issues with the source files...

• Remembering the old D.O.S./Windows 3.1, don't laugh, it was very easy to get a corrupt disk block and have our files buggy, and sometimes unreadable forever...

[PeaShooter_OMO 11]

2 minutes ago, programmerdelphi2k said:

• it was very easy to get a corrupt disk block and have our files buggy, and sometimes unreadable forever...

I would definitely start to look at the hardware

[Lars Fosdal 1793]

Fresh checkout from Git. Compiler does not complain. Program executes fine.  It just that it doesn't appear to be in debug mode.  

[programmerdelphi2k 237]

I once had a problem with a ".pas" not compiling, and, after much thought, the problem was that the file had been changed, for some reason, to a "UNICODE" where control characters (ghosts) had been found (however, they were not visible to the human eye, naturally)...

Solution: I had to redo the file, because even copying it to a non-unicode editor didn't work at all!

[programmerdelphi2k 237]

ok, then it's just DEBUG ...

search PATH to (LIBRARY = dcus / BROWSER =pas / DEBUG = dcu) it's ok on project?

[Lars Fosdal 1793]

See previous posts. Files are in UTF-8 format with BOM.

[programmerdelphi2k 237]

ok! try "check" RELEASE to DEBUG and else and re-save projects... sometimes IDE can be confused!

[programmerdelphi2k 237]

try show all "hide chars" on editor: Tools-User Interface-Editor-Language... options "show"

[Lars Fosdal 1793]

Switched to Release, builded, exited Delphi.

Restarted Delphi, switched to Debug, builded, ran - no change.

 

No weird characters.  Opens fine in TextPad, Notepad, VS Code and IDE.

[programmerdelphi2k 237]

sometimes the Breakpoint dont works if "final-line char" it's not those expected!