I've installed EurekaLog 7, but do not see any EurekaLog-related items in IDE?

Solution:

1. Use Start/Programs/EurekaLog 7/Manage menu item to launch EurekaLog manager (make sure you close IDE before doing that and make sure to run the Manage tool under administrator account).
2. Select you IDE version and click on "EurekaLog 7 with IDE expert" button to install and activate EurekaLog 7 for your IDE.
3. (Optional) If you work under a different user account - you may need to run Manage tool from that account too.

Additionally:

• If the Manage tool does see your IDE, but says that EurekaLog's DCUs are not installed and "Register" buttons are disabled - please, reinstall EurekaLog and make sure that you have your IDE checked during installation.
• If the Manage tool does not see your IDE or if your IDE is not present as an option during installation of EurekaLog - this means that registry entries to your IDE are missing/invalid/broken. EurekaLog uses registry to locate your IDE, so if your registry does not contain correct information - then EurekaLog will not be able to find your IDE.

You can fix broken registry entries:

1. An easiest way is to run "Repair" or "Reinstall" option of your IDE's installer;
2. Alternatively, you may install EurekaLog manually (e.g. using the /Force* command line switches);
3. Finally, you may repair registry entries for your IDE.

EurekaLog installer looks for path values in the registry. For example: HKEY_LOCAL_MACHINE\SOFTWARE\Embarcadero\BDS\8.0\RootDir=C:\Program Files (x86)\Embarcadero\RAD Studio\8.0\. See also this table.

Important: don't forget about Wow6432Node node on x86-64 machines. Check out both HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER.

Additionally, EurekaLog requires personalities to be listed under \Personalities registry sub key for your IDE.

See also:

• Common installation problems
• V6 -> V7 upgrade guide

When I enable EurekaLog for my project in IDE - I get one of the following errors:

• "'true' is not a valid integer value"
• "[dcc32 Warning] W1030 Invalid compiler directive: 'true'"
• "File not found: 'True.dpr'"
• "0" is an invalid value for the "DebugInformation" parameter of the "DCC" task. The "DebugInformation" parameter is of type "System.Boolean"

Reason:

EurekaLog uses OTA to modify options of your opened project. Specifically, EurekaLog must enable debug information. The error messages comes from a known bug (see QC #122547) in Delphi OTA (OpenTools API). Alternatively, it may be caused by opening project in older Delphi version (for example, opening XE6 project in XE3).

Solution:

Try to use any of the following:

A). Switch to "Debug" profile;

B). Delete .dproj file (when downgrading project);

C). Remove all mentions of DCC_DebugInformation from .dproj file (edit with text editor);

D). Go to Project / Options / Delphi Compiler/ Compiling and manually set "Debug information" option to "Debug information" value or "Limited debug information" value. Do not use "No debug information" value.

You have to do this only once.

See also:

• When the Delphi XE5 commandline compiler fails with `error F1026: File not found: ‘False.dpr’`
• MSBuild failing in Cpp.Targets searching for 'True.dpr', with a new XE4 project
• QC Report #122547

Checked:

EurekaLog 7.1, RAD Studio XE5, XE6, XE7.

If I compile my project in "Debug" profile - everything works fine. But if I compile it in "Release" profile - EurekaLog does not work. Even though debug information options are set properly.

Reason:

This is a known bug (archive, QP) in C++ Builder.

Solution:

Sadly, there is no fix so far. You may try to use workarounds (e.g. using "Debug" profile).

Checked EL version: 7.2.2

Checked C++ Builder version: XE2-XE8

Internal Bug ID: 1086

See also:

• I can not debug my application after adding EurekaLog

I do not see "EurekaLog" stage during compilation.

Solution:

1. Check that EurekaLog IDE expert is installed: do you see EurekaLog items in IDE's main menu? If no - you must install EurekaLog IDE expert, either manually or by using "Manage EurekaLog in IDEs" tool;
2. Check that background compilation option is off;
3. Check that show compiler progress option is on;
4. Do you have "EUREKALOG" conditional symbol defined for your build configuration profile?
5. Update all other IDE extensions (such as CNPack) to the latest version.
6. Do you have IDE experts that may modify .map file installed? Such as JEDI (JCL). Check that option to delete .map files is NOT enabled.
7. Do you have any errors in IDE's "View" / "Messages" / "Build" window?

I have installed EurekaLog, but I get "The procedure entry point XYZ could not be located in the dynamic link library ZXY" error message when I start IDE.

Reason:

EurekaLog is compiled against latest builds of IDEs. New IDE builds may be not binary compatible with older builds. Therefore EurekaLog compiled for one IDE build may fail to load with another IDE build. 

Just to clarify: we are talking about same IDE version, but with different builds/updates. For example, RAD Studio 10.3 Rio Update 2 (10.3.2) is not compatible with RAD Studio 10.3 Rio Update 1 (10.3.1) and earlier (10.3). Therefore you have to use EurekaLog built against 10.3.2 with 10.3.2, you can not use EurekaLog built for 10.3.2 with 10.3.1 or 10.3.

Unfortunately, it is not possible to install two different versions of the same IDE on a same machine at same time. Therefore we can not prepare installer which will contain files for each possible IDE update ever.

Solution:

Usually EurekaLog's installer will warn you when you are installing latest EurekaLog's build over old IDE's build.

1. Update your IDE to latest version;
2. Install all available IDE's updates, patches, and hot-fixes;
3. If you are unable to obtain a latest IDE's patches - use older EurekaLog's build (compiled for your update pack).
4. If you want to use the latest EurekaLog build with older version of IDE (without latest IDE updates installed) - you can recompile EurekaLog for your specific IDE version (for EurekaLog Enterprise edition only; comes with full source code).

See also:

• My IDE crashes with EurekaLog 7
• "File XYZ was compiled with different version of ABC" error
• "Could not compile used unit XYZ" error
• "File not found: XYZ" error
• Compiling project with EurekaLog fails with the F2084 Internal Error: URW8074

• Go to "Project"/"EurekaLog project options" and export your project settings (via "Export" button) into standalone .eof file. For example: Options.eof
• Go to "Components"/"Install packages", find EurekaLog IDE package and remove it.
• Create PostProcess.bat file in your project's folder. Use the following content:

  @echo off
  "C:\Program Files (x86)\Embarcadero\RAD Studio\8.0\bin\ecc32.exe" --el_config"Options.eof" --el_alter_exe"YourProject.dpr;YourProject.exe"

• Adjust file paths to ecc32.exe according to your Delphi installation. C++ Builder: replace 'ecc32' to 'emake'. Change file names if necessary (like 'Options.eof', 'YourProject.dpr', 'YourProject.exe'). Please, see this article for more information.
• Now you should call this PostProcess.bat file after each project compilation:
  • Delphi 2007 and above: insert "PostProcess.bat" into "Post-Build Commands" box under "Build Events" tab in project options.
  • Delphi 2006 and below: run PostProcess.bat manually after each compilation or use a 3rd party extension for automatic calling.

I'm using old version of EurekaLog (previous major version). There are new version of EurekaLog available, but we do not plan to upgrade. However, my current version keeps asking me about availability of the new EurekaLog version. How can I disable this dialog?

Solutions:

A). Go to EurekaLog IDE options and uncheck "Check for new version" option.

• For EurekaLog 7 you can find it under "Tools/EurekaLog/IDE options" IDE menu item.
• For EurekaLog 6 you can find it under "EurekaLog/EurekaLog IDE options" IDE menu item.
• For EurekaLog 5-4 - there is no GUI option (see case B below).

B). Manually edit EurekaLog.ini file (located in Windows folder or virtual store - see below). You should add the following lines to it (or alter lines if they are already present)

[IDE]
CanCheckUpdates=0

When editing file or copying it - be awared about virtual store in Windows 7/Vista. Basically, the system behaviour can be altered whenever UAC is on or off.

For best result - edit/replace EurekaLog.ini file in the following locations:

• C:\Windows\EurekaLog.ini
• C:\Users\username\AppData\Local\VirtualStore\Windows\EurekaLog.ini   (replace "username" with your real account name)

If the file does not exist - create it in Windows folder.

You will need to have administrator rights to edit/change C:\Windows\EurekaLog.ini file. The best option is to copy file into another location (say, My Documents), change it and then copy back - Explorer will automatically suggest you to elevate for copying/replacing the file (only for Vista+ - if you're working under administrator account and have UAC enabled).

File in virtual store can be edited/replaced without any additional requirements.

When I've installed EurekaLog 7 - my IDE crashes on startup, during compilation or when exiting.

Reason:

• Delphi and C++ Builder IDEs are 32-bit processes, which are limited to 2 Gb of address space. There are also other known limits (such as command-line length, environment variables length and search paths length). Probably you have too many components and extensions installed, so when you install or use EurekaLog - these limits are reached.
• EurekaLog may conflict with other IDE extensions that also set hooks in IDE. Known examples are AQTime, madExcept or JCL. We're investigating these issues.
• In rare cases there may be a conflict with other external software. Typically antivirus/firewalls.

Solution:

First of all - upgrade to the latest EurekaLog version (your issue may already be fixed).

1. Try to remove unused components and extensions, try to remove search paths for unused components or re-arrange them to move EurekaLog first. If you can not remove any component or extension - then you can use EurekaLog without using EurekaLog IDE expert. Please read this article fore more information.
2. Try setting the "Project" - "Options" - "Delphi Compiler" - "Use MSBuild externally to compile" option to True. This will cause the compiler to run out of process (as a standalone process), which means a bit more free memory to actually do the work.
3. Go to Tools/EurekaLog/IDE options and uncheck "Catch IDE expert errors" options, then restart IDE.
4. Try to disable checking for updates (Tools/EurekaLog/IDE options).

Note:

Please note that limitations of 32-bit processes do not depend on your installed hardware memory (RAM) and disk space.

See also:

I get "Unexpected resource format" error when trying to compile my project. This doesn't happen for new projects.

Reason:

This error may be caused by repeated (double) post-processing of your project. There may be a call to ecc32 in post-build event of your project. Thus, EurekaLog is invoked twice: one for post-build event, second for IDE.

Solution:

Go to Project/Options/Build events and remove call to ecc32.exe from post-build event. If you want to have this command (for compilation outside of IDE) - then switch your project to manual control as explained here.

If this is not your case - please, contact our support. Send your .exe file for analyzing (it doesn't have to be runable).

I set "Application type" option to "VCL Forms Application". However, when I open options dialog again - this option is reset to default "Custom settings / unsupported application".

Reason:

"Application type" combo box is not a standalone option. This is like "templates". When you select value from combo box - then some other options for your project will be set according to the selected template. For example, when you select "VCL Forms Application": hooks for Application.ShowException will be used. Also, dialog will be switched to MS Classic, DLL exports reader (debug information provider) will be included, etc.

This means that if you manually change some option to another value - then your settings will not match the selected template. That's why "Application type" option will be reset to default "Custom settings".

A common reason for "Application type" option being reset is usage of "EurekaLog 6 compatibility mode". EurekaLog 6 didn't have concept of application types. That's why when you enable EurekaLog 6 compatibility mode, "Application type" option will be reset.

Solution:

Just do nothing. If you changed some options to match your needs and desires - then there is no need to revert it back (by re-selecting application type) just to see (for example) "VCL Forms Application" value in "Application type" combo box.

If you want to know more about which options are affected by "Application type" combo box - see description of application types in help.

See also:

• Application types
• Compatibility mode

My EurekaLog-enabled application generates bug reports in encrypted form, but I didn't specify any password. What is this default password?

Reason:

Most probably that your EurekaLog settings was corrupted.

Note: in some cases "corrupted" means correct, but unknown format. For example, different EurekaLog versions stores options in slightly different format. This may cause problems when opening same project in two different EurekaLog versions. Usually this happens when downgrading EurekaLog - because new EurekaLog version can recognize older format and convert it, but older versions are not awared of the format of the new EurekaLog version, which may cause wrong settings to be set.

Solution:

Remove EurekaLog configuration from your project and re-setup it:

1. Close your project in IDE. 
2. Make a backup of your project files (only project files, no units).
3. Open your project configuration file (.dproj, .cbproj, .bdsproj, .dof, etc.) in any text editor (like Notepad).
4. Find block with EurekaLog configuration at the end of the file.
5. Remove it and save file.
6. Re-open your project in IDE.
7. Re-setup EurekaLog options.

Alternatively, if you not able to remove EurekaLog configuration from the project - just walk through all EurekaLog options and re-setup them.

I can not debug my application/DLL. All breakpoints are non-functional.

Reason:

There may be several possible reasons for this. This issue is not specific to EurekaLog.

Solution:

• First, be sure to (re-)setup debugging options as explained here. Be sure to enable debug information and be sure not to have directives like {$D-} in your code.
• Check file paths:
  • Be sure that you don't have two different units with same name in different folders (i.e. new and old files). You may load wrong unit in editor, but debugger will operate on another unit.
  • Be sure that output folder for units is listed as library search path (per-project setting).
  • Be sure that your file is included in project and it will be compiled with the project:
    • Check search paths of the project;
    • Check used files (with explicit file paths) in .dpr/.dproj files (Project / View source).
• Delete old files (*.dcu, *.obj, *.lib, *.tds, *.rsm, *.bpl, *.dcp, *.exe, *.dll) and build your project(s) (not just make/compile).
• It's possible that you've opened file that do not belong to project. File may be already compiled or it may be not part of the project (think about exe/DLL).
• It's possible that your project is DLL and DLL wasn't loaded by host process. Breakpoints will not work until DLL is loaded. Sometimes DLL may be not loaded at all.
• It's possible that code with breakpoint isn't used in your project. For example, a unit can contain 3 functions. Functions #1 and #2 are called from the program, but function #3 is not. Thus, breakpoints in function #3 will not work. Similarly, optimized compiler may remove individual lines of code from the functions. For example, code line calculates value, but this value is not used anywhere. Such code will be omitted from final executable.
• It's possible that your code is placed in run-time package (.bpl). Thus, rebuilding your project will not affect that unit. And that unit (in package) may be compiled without debug information. If this is the case - then you need to either rebuild package with debug information or remove package from being used in your project.
• It's possible that debugger can not associate running program with your project. To avoid this:
  • Do not rename application and DLLs. Name project files with desired names.
  • Do not move application and DLLs to other folders. Setup proper output folder instead of moving files. This is especially true for DLLs and Win32 services.
  • Do not run application (don't load DLLs) via alternative names. For example, the same folder can be accessed via different names (folder itself, hardlink, via mapped network share, via reparse point, subst-drive). So, if you can access the same file/folder with different names - be sure to use exact same name in all places. This is especially true for DLLs, because they are loaded by host process (which may be not controlled by you). You can use Process Monitor or similar tool to check file accesses.
  • Be sure that all file paths contain only ASCII symbols (latin). Do not use local symbols with codes above 128.
  • Do not alter date/time (date of creation or modification) of compiled files and .dcu/.obj/.lib files. Changing date/time may cause debugger to consider files being changed. "Changed" files requires recompile, thus they do not match each other. Sometimes date/time can be changed by anti-virus software or post-processing tools (like digital signing).
  • Do not delete and do not move .dcu/.obj/.lib files. Be sure to setup unit output folder to the right place. Be sure that unit output folder is listed in library search paths. Try to place .dcu/.obj/.lib files in same folder as .exe/.dll/.bpl/.dcp files.
  • Be sure that all files can be found. Specify search paths or include unit explicitly via "Project / Add to project" command.
  • Try to enable TD32 debug information.
  • As extreme case - try to output all files in single folder. I.e. output .dcu/.obj/.lib/.exe/.dll/.bpl/.dcp files in folder with source files.

See also:

• I can not debug my application after adding EurekaLog

I develop IDE package (component or expert). When I compile my package, no EurekaLog information is added, even though package is configured with EurekaLog. Instead, a message "Package is installed in IDE. It's not possible to modify .bpl file" is shown in IDE's messages window under "EurekaLog" node.

Explanation:

This is a limitation of IDE's OpenTools API.

You have your package installed (registered) in IDE. Thus, your package is loaded by IDE process. This means that no one can alter it. When you compile your package in IDE, IDE unloads your package, recompiles it, then loads it back.

EurekaLog IDE expert assigns "AfterCompile" event via IDE's OpenTools API. Unfortunately, this event is triggered after compiled package is loaded back in IDE. Thus, EurekaLog code can only see your package when it was already reloaded back to IDE. Therefore, EurekaLog IDE expert is unable to modify your package.

Solution:

1. Manually unload (unregister) your package in IDE, recompile it (since package is not loaded - this time EurekaLog will be able to alter it), then install/register it back.
2. Manually invoke EurekaLog's post-processing before package is loaded. Specifically, project's post-build event (not to be confused with EurekaLog's post-build event) is executed when compiled package is unloaded. In other words, you have to place a call to ecc32 to your project's post-build event as described in this article.

Checked EL version: 7.3.1

Ticket ID: 10965 (GIR-315-42360)

I get "out of memory" exception from ecc32 when compiling my large project with EurekaLog.

Explanation:

EurekaLog's ecc32 uses arrgessive memory allocation to speed up post-processing. Doing so it can post-process smaller projects in a matter of few seconds (sometimes even less than one second). However, if you try to compile larger project in this mode - ecc32 would run out of memory, as it is 32-bit process limited to 2 Gb of address space.

Solution:

You can instruct ecc32 to conserve memory usage. The post-processing will be slower, but it will use far less memory. To do that:

1. Open "Project" / "EurekaLog options" dialog;
2. Go to "Advanced" / "Custom / Manual" tab;
3. Add the following option to any location:

ECC32TradeSpeedForMemory=1

Note: be sure to check if such option already exists (the options' list is sorted alphabetically). The option is not presend by default, but someone may already added it. If this option exists - replace '0' with '1'.

I get the following messages when trying to compile or install my own package, 3rd party package, or 3rd party framework:

• "The following changes are necessary to make this package compatible with other installed packages. Choose OK to apply these changes and rebuild the package: Add EurekaLogCore. EurekaLogCore contains implicit unit(s) Web.Win.IsapiHTTP".
• "Cannot load package 'my-package.' It contains unit 'Web.Win.IsapiHTTP', which is also contained in package 'EurekaLogCore'."

Reason:

1. Same unit may not appear in two or more loaded packages;
2. Web.Win.IsapiHTTP unit is not included in any default RTL/VCL package, which means this unit became part of any package that references this unit.

E.g. Web.Win.IsapiHTTP becomes part of EurekaLogCore package, your own package / 3rd party package / 3rd party framework.

Solution:

You need to move Web.Win.IsapiHTTP unit into a new package, which will be shared by all other packages that need Web.Win.IsapiHTTP unit:

Step 1: prepare shared package:

1. Create new run-time package;
2. Add Web.Win.IsapiHTTP unit to this package ("contains" section);
3. Add rtl, vcl, inet packages to "requires" section;
4. Build modified package.

Step 2: redirect other packages to use new shared package:

1. Open EurekaLogCore package (available in EurekaLog Enterprise);
2. Add package name from previous step to "requires" section;
3. Rebuild the package;
4. Use "Manage EurekaLog in IDEs" tool to reinstall EurekaLog.

Step 3+: repeat "Step 2" actions for your own packages, 3rd party packages, 3rd party frameworks.

IDE may stop executing my application when I run it under debugger. IDE opens a new tab in code editor with EurekaLog's unit. However, there is nothing useful inside, just a lot of repeating "// You do not have source code" lines.

Reason:

1. You are using Trial or Professional editor of EurekaLog (e.g. without source code). These editions of EurekaLog come with headers only (e.g. interface sections). That is why all implementation sections are empty (filled with "// You do not have source code" comments);
2. The reason why you have stopped inside EurekaLog's unit may vary:
   • EurekaLog may want to draw your attention to the problem which happened in your application;
   • There may be an exception inside EurekaLog's code.

Solution:

Check call stack of your application (View / Debug Windows / Call Stack):

1. If you are inside ELowLevel.DebugBreak function - it means that EurekaLog is trying to get your attention, because some important issue was found in your application. Typically, it would be some memory problem (see also: "Use safe mode to handle special exceptions" option). You are supposed to inspect the problem before EurekaLog will process it. You can also continue execution to let EurekaLog process exception as usual. This happens ONLY when you are running under debugger;
2. If you are in any other location - it usually means that there was an exception in EurekaLog's code. This could be an expected exception, as well as a bug in EurekaLog. Simply continue execution and see if application will behave as expected.

If you are still uncertain about this case - you can always create a run-time log. This log will show everything that is happening in your app. You can send us the resulting .csl file (packed in any type of archive), so we can investigate it and provide an explanation.

See also:

• "Use safe mode to handle special exceptions" option

I am getting the "No frames are available to insert" error when I am trying to insert a frame on the form after I have enabled EurekaLog for my project with frames.

Reason: 

Unfortunately, this is a bug in IDE.

EurekaLog uses the official OpenTools API (OTA) to integrate with IDE. When you are enabling EurekaLog for your project - EurekaLog edits .dpr file to insert units and this confuses IDE.

Specifically, IDE offers IOTASourceEditor interface, which has CreateWriter method to obtain a IOTAEditWriter interface. EurekaLog uses methods of IOTAEditWriter interface to edit content of .dpr file (basically, this is just a series of .DeleteTo and .Insert). Apparently this is somehow forces IDE to corrupt .dproj file.

Solution:

Once you have enable EurekaLog for your project - close your IDE and open .dproj file in any text editor. Search for name of your frame. You should find something like this:

    <ItemGroup>
        <DelphiCompile Include="$(MainSource)">
            <MainSource>MainSource</MainSource>
        </DelphiCompile>
		...
        <DCCReference Include="UnitFrame.pas">
            <Form>Frame1</Form>
            <DesignClass>TFrame</DesignClass>
        </DCCReference>
		...
    </ItemGroup>

Add the FormType tag like this:

    <ItemGroup>
        <DelphiCompile Include="$(MainSource)">
            <MainSource>MainSource</MainSource>
        </DelphiCompile>
		...
        <DCCReference Include="UnitFrame.pas">
            <Form>Frame1</Form>
            <FormType>dfm</FormType>
            <DesignClass>TFrame</DesignClass>
        </DCCReference>
		...
    </ItemGroup>

Please note that the order of tags are important.

Repeat these steps for each frame in your project.

Save changes and reopen your project in IDE. It should work as expected now.

I can not debug my application in IDE after I have added EurekaLog. IDE's debugger is either fails to start / load or it runs executable with disabled breakpoints and no source code debugging.

P.S. Possible error message from IDE: "Debugger fatal error: debug kernel not responding. The debug process will be terminated."

P.P.S. It may happen in C++ Builder only.

Reason:

EurekaLog needs to change your executable by adding (injecting) debug information. Debug information is stored as an additional PE section. Our code takes extra care to keep changed (after injection) executable as similar to the original as possible: including restoring file timestamps, recalculating PE header CRC, etc.

However, sometimes it is not enough for IDE's debugger. It may fail to recognize your executable after modifications. Unfortunately, we are unlikely to fix such issue from our end, as IDE's debugger is essentially a black box for us with little to no control. What we can do is a bit of woodo magic, trying to understand things that it does not like.

We have reports from our customers that sometimes C++ Builder refuses to debug executable. Either failing to load / run, or running executable without debug information (e.g. breakpoints are disabled; no source code debugging, etc.). On the other side, we did not have a single report about such cases for Delphi.

Solution:

1. Report the issue to the Embarcadero's bug tracker;
2. Upgrade to the latest IDE;
3. Apply/install all latest IDE's service packs / updates / patches;
4. Switch "Debug Information" option from "Inject" to "Add";
5. If the above does not help - go to "Project" / "EurekaLog options" / "Advanced" / "Custom/Manual" and look for the DoNotTouchEXE option. If not found - add it like so:
   DoNotTouchEXE=1

Important Notes:

Switching the "Debug Information" option from "Inject" to "Add" (or using the DoNotTouchEXE=1) is supposed to be a temporal workaround for debugging. Please note that your executable will not be self-sustained with either of these options:

• you need to deploy .edbg file with your executable;

or

• recompile with "Inject" (DoNotTouchEXE=0) option for production.

Please note that if you use the DoNotTouchEXE=1 option - then EurekaLog will not touch (open) your executable at all. So if you still have your issue while using that option - then EurekaLog has absolutely nothing to do with the issue.

See also:

• Debugging / breakpoints are not working (non-EurekaLog related)
• RSP-29696 C++64: Debugger fatal error: debug kernel not responding. The debug process willl be terminated
• EurekaLog does not work when compiling "Release" profile in C++ Builder