CODEWITHSUNDEEP
delphisettingsdevelopment-environmentbreakpoints
Nemanja Vujacic
Nemanja Vujacic

Reputation: 935

Delphi 6 doesn't trigger breakpoints

After installation of Delphi 6 at new working station I issued problem with breakpoints. In debug mode environment doesn't trigger breakpoints like they are not placed at all...

Have you experienced similar situation? I suppose reason is some setting, but I cannot find which one...

TnX in advance!

Nemanja

Upvotes: 4

Views: 4302

Answers (2)

Nemanja Vujacic
Nemanja Vujacic

Reputation: 935

I applied all settings that @Gamecat suggested, so you can look at this answer like short addition to previous answer.

I missed only one more to solve my problem. In Tools>Debugger Options I checked Integrated Debugging which alive my breakpoints. When breakpoints started to work, I got error message 'Project _.exe raised exception class EAccessViolation with message 'Access violation at address 4CDEB080 in module 'IDPDX32.DLL'. ' For solving this issue I just unchecked option 'Stop on Delphi Exceptions' in menu Tools>Debugger Options>Language Exceptions.

Now Delphi works fine and don't need to reinstall it.

Reason for loosing my previous configuration that worked fine might be in copying my files from one folder to another (as well as config and other temp files) when paths became wrong and after that I probably deleted old config files and started with settings from beginning...

+1 Tip: If you get this message: [Error] RLINK32: Unsupported 16bit resource in file ....\estands\estandar_StdFormMainFrm.DFM problem is in Text-DFM option. When you right-click on the form in the IDE, is the menu item "Text-DFM" (or maybe called "Text as DFM") checked? If not, do so, save and try to compile.

If somebody knows reason for this behaviour, detailed explanation would be useful. Until now I found this option is for backwards-compatibility to older Delphi-versions.

Upvotes: 2

Toon Krijthe
Toon Krijthe

Reputation: 53366

Yes, this sometimes happens (not only in 6).

  • Enable all debug information except debug DCU's unless you want to debug the Borland code. (Don't forget to check for compiler switches in the code).
  • Disable code optimizer.
  • Rebuild all code.
  • If you are using DLL's be sure to enable debug code in all projects and set the host application to the right executable.

If that fails.

  • Be sure that there are blue dots at the code.
  • Be sure you have the right source file. You can check this by adding an error (for example dghasgsgd) and recompile, if the compiler accepts, this is not the right source file.
  • Be sure the code is reached (add a SendMessage statement or a message box so you can be sure the statement is reached.).
  • Restart the compiler. Or even restart the pc.

If that fails.

  • Take a break. Have a lunch or get something to drink.
  • Return and show the problem to a coworker. (preferably a programmer too).

Upvotes: 7

Related Questions