Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: C++ Builder Seattle, linker problems + clang compiler problems


This question is not answered. Helpful answers available: 2. Correct answers available: 1.


Permlink Replies: 4 - Last Post: Dec 6, 2015 5:40 AM Last Post By: Petr Vykouk
Rutger den Boer

Posts: 3
Registered: 3/21/02
C++ Builder Seattle, linker problems + clang compiler problems  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Nov 9, 2015 1:07 PM
Hi,

I got a few questions, hope someone can point me in the right direction. It's all to do with C++ Builder Seattle.

A small newly set up vcl project works fine compiled with clang 32-bit. Switching to 64-bit produces an ilink64 error: ELF232. I'm a 100% sure that the application did link 64-bit a short while ago. No information on the internet about ELF232.

After some effort converting a huge VCL project to compile with the clang 32-bit compiler, it crashes after calling Application->CreateForm(). Debugging is only possible using the CPU view and stepping through the instructions or else it crashes the debugger when entering the constructor of the main form. The resulting message is 'Debugger Fault Notification' .. raised too many consecutive exceptions: 'access violation at 0x.....: read of address 0x00000000.'. Switching to the classic Borland compiler: no problems what so ever. [By the way, the crash occurs in Vcl::Forms::TApplication::CreateForm 'call dword ptr [ebx+$3c]']

Another huge application was modified to compile with the clang 32bit compiler, compiling works fine but the linker returns error ILI2008 preceded by a lot of ilink32 warnings starting with Warning: BSS : 0x00000000 / 0x01000000, CODE, DATA, DEBNAM, DEBSYM, .... , Virdefs and last warning is 'unknown heap name': 0x08000000 / 0x08000000. Again, switching to the BorlandC compiler solves all problems.

Can anyone point me in which direction to look for code issues regarding
1. ilink64 error ELF232
2. 'raised too many consecutive exceptions'
3. ilink32 error ILI2008 combined with a lot of warnings

Thank you very much, any comments are much appreciated
bernard roussely

Posts: 106
Registered: 2/8/05
Re: C++ Builder Seattle, linker problems + clang compiler problems  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Nov 16, 2015 2:35 AM   in response to: Rutger den Boer in response to: Rutger den Boer
Hi,

Don't know about ELF232. Just about ELF: https://fr.wikipedia.org/wiki/Executable_and_Linkable_Format. Looks weird for a VCL application.

For the crash of the converted VCL app, this is frequent and difficult to trace. You most likely have an access violation within some library. Possibly rebuild the code incrementally until you find the module/lib that causes the crash. You may have conflicting lib versions and you may be willing to clean up your project file.

Best of luck,

bernard
Martin van der ...

Posts: 57
Registered: 7/14/02
Re: C++ Builder Seattle, linker problems + clang compiler problems  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Nov 16, 2015 4:00 AM   in response to: Rutger den Boer in response to: Rutger den Boer
Linker errors are perhaps caused by the compiler not rebuilding everything it should. The clang compiler has some trouble with source file dependencies. Have you tried a full rebuild?
Other than that, I can only recommend not using the clang-32 compiler for the time being. It's pretty much unusable in its current state.
Rutger den Boer

Posts: 3
Registered: 3/21/02
Re: C++ Builder Seattle, linker problems + clang compiler problems  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 5, 2015 4:52 AM   in response to: Martin van der ... in response to: Martin van der ...
Thanks for the replies. No solution found yet, unfortunately. To me it looks like Embarcadero is very busy releasing new buggy features forcing users to buy the upgrades instead of focusing on stable releases of compiler and linker..
Petr Vykouk

Posts: 42
Registered: 6/4/00
Re: C++ Builder Seattle, linker problems + clang compiler problems  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Dec 6, 2015 5:40 AM   in response to: Rutger den Boer in response to: Rutger den Boer
Rutger den Boer wrote:
Thanks for the replies. No solution found yet, unfortunately. To me it looks like Embarcadero is very busy releasing new buggy features forcing users to buy the upgrades instead of focusing on stable releases of compiler and linker..

Yes,

you are Right. Seattle 10 after UPD1 is still very buggy. My lates IDE fully usable is XE8.1.
Marco Cantu is over-optimistic about Quality of Seattle 10 CBB.
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02