Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3348404
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 18, 20262026-05-18T01:32:19+00:00 2026-05-18T01:32:19+00:00

Sometimes as I am debugging step-by-step, just before a FormCreate Event or just after

  • 0

Sometimes as I am debugging step-by-step, just before a FormCreate Event or just after the FromDestroy the debugger starts to open DevExpress units (cxContainer.pas, …) and so before FormCreate my “F8” leads me to cxContainer instead of going into the next line of my code.

(this is just an example, it can happen of course with any 3rd party library)

How do I tell the debugger “debug only my units” (only the pas files listed in dpr file?)

Of course sometimes it is useful to debug libraries, but in most cases it isn’t.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-18T01:32:20+00:00Added an answer on May 18, 2026 at 1:32 am

    You’d better follow VCL convention for your third-party components:

    • Change DCU output path in all the third-party packages to a folder different than the folder you store the PAS files.
    • Compile each package once in Debug mode, and save the generated DCU files in a folder (e.g. Debug DCUs).
    • Compile each package once again, but this time in Release mode, and save the generated DCU files in a folder (e.g. Release DCUs).
    • Go to Delphi options and add path of release DCUs to “Library path”.
    • In Delphi options, add path of source files to “Browsing path”.
    • In Delphi options, add path of debug DCUs to “Debug DCU path”.

    This way, Delphi will only see release DCUs of that third-party component when you are compiling your project, so the debugger cannot step into the source code.
    On the other hand, since source path is included in “Browsing path”, you can still navigate to the source code inside IDE by Ctrl+Click on unit name, or anything defined in those units.

    If you want to debug component, you can go to “Project | Options | Delphi Compiler | Compiling”, and enable “Use debug .dcus”. This will force compiler to use “Debug DCU path” instead of “Library path”.

    VCL works the same, generally you don’t step into VCL source code when you are debugging your project, but if you enable “Use debug .dcus” you can debug VCL source code too.

    JVCL also organizes its packages and source code the same way.

    EDIT:
    If you take this approach, and want to have code browsing (Ctrl+Click) working; please take note that when you compile release version of packages, you must set Symbol Reference Info in “Project | Options | Delphi Compiler | Compiling” to “Reference Info”; otherwise, Ctrl+Click won’t work for those units. By default, Release build configuration sets Symbol Reference Info to None.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Occasionally during debugging the debugger skips forward randomly. Sometimes I Step into a function
Sometimes while debugging, I need to restart a service on a remote machine. Currently,
Sometimes when I am debugging code in Eclipse it happens that although I can
I'm debugging an ASP.NET application but sometimes cannot find w3wp neither in Visual Studio
sometimes, when I use Form.close() when debugging my program, although the form is closed,
I'm android developer and I use Eclipse. Sometimes, when I am debugging my apps,
Sometimes when I'm editing page or control the .designer files stop being updated with
Sometimes IE6 will render the text of a <ul> list the same color as
Sometimes I need to quickly extract some arbitrary data from XML files to put
Sometimes I have to work on code that moves the computer clock forward. In

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.