Debug buttons are disabled in Delphi 2007 IDE. I can build project with command line or Project -> Build, but cannot run application or either attach to process.
I'm wondering if anyone has encountered this issue in the past and can help me.
Few facts:
Delphi 2007 IDE was installed on my machine and worked just fine.
Debug buttons got disabled at one point of time and I have no idea what was the reason.
I tried reinstalling Delphi, but this did not help.
License for Delphi is ok.
I suppose that there should be
something with either registry or 3rd
party components.
I'm .NET developer and need investigate some piece of Delphi code, so please do not blame me :)
Will appreciate any help.
Possibility...
Go to pull down menu: 'Project/Options/Compiler' and set in field 'Build Configuration' to 'Debug'. In filed 'Debugging' switch-on first 5 switches like 'Debugging Informations' and so on!
So, as I figure it out later (from Delphi developers from different team) issue was with 3rd party components to Delphi. They stored something into registry. It was enough to change some registry keys, they did this so I cannot post it here.
Very interesting how it could be that such components got shipped.
Related
I have just installed Community Edition of Embarcadero C++Builder 10.3, as downloaded from the manufacturer's website. When I run it, the Welcome screen looks OK. Then I press on "Create a new Windows VCL application - C++" link to create a simple "Hello World" GUI project targeted at Windows. After that things fall apart - the windows in the RAD Studio do not update, and the only way to get at least some information out of them is to click on them (see screenshot below). And even then their headers never show up. Main toolbar is entirely lost. Main menu is only visible when you click on it. And then the main menu becomes frozen for several minutes. I can't even get to just placing a simple button on the form, let alone writing some code.
I used to be a huge fan of Delphi 20 years ago, did a lot of software development in it, then migrated to MSVC. Now I am trying to migrate back to Delphi/C++Builder tools, so I gave it it a try. But come on, it can't fall apart right after the installation while attempting "Hello World" project! Not a development tool that has decades of history! Am I doing something completely wrong? I really want this tool to work out for me, I have lots of respect for it from 20 years ago.
I installed C++ Builder 10.3.3 community and opened an example VCL project "Searchbox".
It compiled and ran the program, but I am not able to navigate in the sourcecode.
If I hover the mouse over a datatype or variable, a tooltip appears "cannot find C:/Users/Public/Documents/Embarcadero/Studio/20.0/Samples/CPP/VCL/SearchBox/usearchbox.cpp" This is the file in the editor and it definitely exists, however note the path is written with forward slashes, this might be the reason of failure.
If I search for declarations via menu, nothing happens, no result, no error.
To me, this seems to be (partially) broken out of the box.
My OS is Win10Pro 64 Bit.
Edit:
This apparently only happens when the classic Borland compiler is deselected which means CLang is used.
Because I am only interested in the CLang compiler, the product is -unfortunately- unusable for me.
With XE8 update 1, Win 7 64 bit and a single component added to an otherwise empty folder I get:
error: [dcc32 Fatal Error] F2039 could not create output file .\Win32\Debug\MountTest.
The test will compile and run fine the first time but XE8 has to be shut down and restarted to compile again. The component is a gauge from Mitov Software.
The component vendor say's that this is a known bug with no fix. If so its a showstopper and project end'r for me. Is it really the end of the line for Delphi?
I hope some one can pull this rabbit out of a hat somehow.
This is what I have done to isolate the problem.
Started with a failing application (will not compile a 2ed time)
Remove all external units used
Remove al references to those units
Remove all references in the 'Uses' clause
Comment code until it compiles
It should compile every time you hit run (no problem).Now add a blank form to the project. Don't do anything to the form just add it. Add it to your uses clause.
Its should compile every time you hit Run.
Now open the blank form and simply touch it so that it needs to be recompiled.
When you run the application its back to failing when you run it a second time.
Notice that happens when you simply add a form and 'touch' it. No code needed.
This problem is not something wrong with my code - it can't be. Its a bug in the UI - must be.
Coincidentally, I just fought with this issue yesterday testing some components I ported to XE8. The output file in my case is the project executable.
After spending several hours trying to figure out what was going on (including efforts to reconfigure my AV software, disabling it entirely, moving the project to a different location, etc.), I was able to solve the problem by disabling Castalia. If I run the IDE without Castalia, the problem does not occur. If I enable Castalia again, it starts happening again.
You can find instructions for disabling/enabling Castalia in How can I disable Castalia in XE8?
I'm removing the above content because the issue has reappeared (with Castalia disabled). Further investigation shows a couple of things:
The problem seems to be related to any sort of exception being raised in the debugger (even those that are handled in the code). Clicking either Break or Continue in the debugger exception dialog works as always. However, the next attempt to compile or build the application fails with the F2039 error. Deleting the executable in Windows Explorer allows compilation and running once, and then the error recurs.
Restarting the IDE fixes the issue, until the next debugger exception occurs.
Neither taskkill or a batch file with del worked in either a pre- or post-build event.
There is an open QC entry for it at Embarcadero which indicates that it was reported in XE7, XE7.1, and XE8, and is currently an open internal ticket. I can't find a way to add the information in the two points above to that open ticket in the new JIRA-based Quality Portal. Perhaps someone who has access and can do so will on my behalf (or at least add a link to this post).
It's not linked to a specific project. The original answer (as mentioned above) was related to a test app while porting some components to XE8 from an earlier version. When the problem reappeared for me, it was in a brand new project, totally unrelated, that does not use any non-standard components.
(I previously had access to EMBT QC, and had a few open tickets. The accounts appear to have not migrated to the new QP, and I can't locate any tickets there under my account.)
Found It.
I decided to start from scratch on my development system and uncovered the problem.
I installed Windows 10 on a virgin disk
Installed XE8 update 1
Installed MITIOV Instruments for XE 8 and tested them. All working find
Installed AsyncPro - Still working
Installed the JEDI Jcl - Fails
Remove JEDI Jcl - now works
Trash JEDI completly - Everything works fine
Something in the JEDI Jcl version 3.48 is causing the problem. I can code around the JEDI components I was using without to much trouble but its a shame.
How about automatically kill your "hang-up" application before build?
I also had this problem on Win 7 Pro 64 bit with XE8.
Removing JCL fixed the problem. If I was a betting man, I would look closer at the JCL Debug IDE extension.
Guy's..
There is no reason to upgrade to Delphi 10.1, because all previous versions are equipped with an older version of the Android SDK.
Now, how to solve this annoying issue:
Just find the map where the Android SDK is located.
See: Tools/Options/Delphi Options/SDK Manager/Android Location
Now run the ..\sdk\tools\android.bat as Admin
This will show the Andoid SDK Manager.
Next is to update to the newest Android SDK and SDK Tools.
If all completed, you don't have to upgrade to Delphi 10.1 or whatever "advised".
Restart Delphi and problem:= solved!
btw:
It took some effort to find out what's happening here, because the Eclipse compiler suffered the same issue as Delphi. Finally all was related to bugs in earlier versions of the Android SDK causing adb.exe to keep a filehandle held hostage.
I'm new to StackOverflow, and generally find the answers I'm looking for here. Except this time. I'm confuzzled. Here goes:
Some weeks back, I downloaded Revision 306 of Delphi Chromium Embedded, and installed it on a fresh copy of Delphi XE. Now, this was grabbed from the "Downloads" section of the DCEF Google Code page.
First thing I noticed was that the site mentions that Delphi XE is supported, but there is no project package included specifically for XE. Naturally, I installed the package meant for Delphi 2010, as the one for XE2 won't work due to FMX, and perhaps a few other things (?).
Having used an older build on D7 in the past, I naturally dropped a TChromium on the form, set the default URL to http://foundry-local/assist/node/, and ran the app. Here's what I was greeted with:
Exception EExternal Exception in libcef.dll ... External Exception 80000003.
Couldn't post anything in their new Google Group (they disabled the issue tracker on the Code page), so I thought I'd come here to figure out what happened. But just before that, I decided to checkout the latest code-build from the trunk. Installed it successfully (still no package for XE), dropped a TChromium on a blank form, and ran the app. This time I was greeted as follows:
Exception EReadError in module FoundryAssistNodeManager.exe at 0004BE24. Error reading Chromium1.Options.AcceleratedCompositingEnabled: Invalid property path.
And hence: I am really confuzzled.
(Edit: The app can see the core libraries, and they are being picked up.)
Has anybody else been having problems using DCEF on Delphi XE? If so, anyone had some kind of solution?
See, I'm building a customised help platform for my to-be-released products. Using IE is unreliable, and Gecko's components are no longer in development.
Any tips, guidelines would be great. Thanking you all in advance.
Technically speaking, this is not an answer to my question, but I feel it is necessary to show viewers of this question the best route to take.
Quite simple really: Upgrade to DCEF3.
Some developers local to me have also reported the same problem, with no apparent fix. Using version 3 solves the problem.
To the commenters above, thank you for helping as far as you could. Much appreciated.
After upgrading to Windows 7 all seems to work in my Delphi 2007 version except this one.
I know that 2007 is not build for win 7 but I'm not sure that the OS is the reason. My friend is using it without a problem.
When I use "Find Local References" all is fine.
Do you know a fix for this? Some dll registration may be?
I found the solution!
When I used Refactor -> Rename menu delphi didn't blew up but kindly show me the error. Unavailable interface call with the name of it.
So after short research I've registered 2 tlb files and all is working now.
..CodeGear\RAD Studio\5.0\bin\Borland.Studio.ToolsAPI.tlb
..CodeGear\RAD Studio\5.0\bin\Borland.Studio.Interop.tlb
I used tregsvr.exe for the registration without a problem under my x64 system.
P.S. I still wonder what else is not registered during the installation .. hopefully all is good.
I'm running windows 7 ultimate (32bit) and have a very anoying problem with my installation of delphi.
The problem is with the feature "Code Insight" and with "Code template completion", it is very anoying when it every time i write something and it wants to complete some piece of code for me (for example i hate it when he completes the for condition). The problem is that i can't shut it down since i think it has a bug when installed on windows 7 that when i turn those features off it works once and then it turns on again, like it couldn't write in the settings file.
Does anybody know where Codegear Delphi 2009 stores it's setting/configuration file? Or how can i turn off.
I tried running it as administrator in compatibility mode (vista and xp) tried searching for the file but with no luck.
In the registry under: HKEY_CURRENT_USER\Software\CodeGear\BDS\6.0
Also in HKEY_LOCAL_MACHINE\SOFTWARE\CodeGear\BDS\6.0 but there seems to be no data there of interest.
Also under C:\Users*USERNAME*\AppData\Roaming\CodeGear\BDS\6.0 are some settings stored.