Linking Executable error when debug in 64Bit: #main.o: undefined symbol

anon20074439 · February 14, 2019, 2:00pm

Put a feedback support ticket in and see if Xojo can provide you a way to reduce lld to a single thread.

Aditya_Nugraha · February 14, 2019, 2:16pm

Yeah man, putting in here just in case others newly experiencing the same thing and found out the real fixes.

I invest quite heavily on this workstation, it’s quite a bummer if using it without Hyper-Threading, even tough Intel being rumored will be moving away from Hyper-Threading.

Intel being too long in the highest of ‘food chain’ and forgetting its known reliability, stability, security. The ‘throne’ will move away from Intel.

Edit :

Hmm quite possibly about single thread Xojo linker or as you know based on LLVM 6.0.0 is heavily threaded, but i will ask.

anon20074439 · February 14, 2019, 2:32pm

I’m so gutted for you, that is a really nice chip and not a cheap chip, its so unfortunate that this issue crept into it and it seemingly hasn’t been fixed.

I really hope someone at Xojo can sort you our with either a few special builds to test or something.

Maybe someone at Xojo has a contact at Intel whom they can ask for a test sample because its prohibitively expensive to expect someone at Xojo to buy one just to test this edge case. They send these things out all day long to reviewers on YouTube it might not be a far stretch for someone to reach out to Intel.

Failing that, I hope Asus/Intel can get to the bottom of it some time this century.

So gutted, I’d be fuming, any chance of an RMA for a different chip?

Aditya_Nugraha · February 14, 2019, 3:15pm

Tried Asus forums for my mainboard type and there is no help, getting the vibe of RTFM & use/change into Intel c/c++, just like *nix/linux/BSD communities.

Yes, i am sure Xojo has contact with Intel.

I have already spent nearly 1 month for communication back and forth with Asus America, and finally they suggest for closure looks by RMA.

LOL

Planned to change/cleaning up the motherboard or memory. RMA in my country probably takes around plus minus 2 month, so i need either way change the motherboard.

Aditya_Nugraha · February 15, 2019, 4:54am

And again the feedback got closed, after updating into modded motherboard bios for newest intel microcode, now Xojo failed to invoke the Xojo linker :

[quote]Linking Executable
Failed to execute linker: Error 740:[/quote]

From debugview :

[quote]00000109 44.99749756 [11956] C:\Program Files\Xojo\Xojo 2018r4\Xojo.exe
00000110 44.99773788 [11956]
00000111 45.99752808 [11956] C:\Program Files\Xojo\Xojo 2018r4\Xojo.exe
00000112 45.99759293 [11956]
00000113 46.69392014 [12080] pre build
00000114 46.99750519 [11956] C:\Program Files\Xojo\Xojo 2018r4\Xojo.exe
00000115 46.99755478 [11956]
00000116 47.99935532 [11956] C:\Program Files\Xojo\Xojo 2018r4\Xojo.exe
00000117 47.99943542 [11956]
00000118 48.99900818 [11956] C:\Program Files\Xojo\Xojo 2018r4\Xojo.exe
00000119 48.99907303 [11956]
00000120 49.99816132 [11956] C:\Program Files\Xojo\Xojo 2018r4\Xojo.exe
00000121 49.99818420 [11956]
00000122 50.02987671 [12080] Failed to execute linker: Error 740:
00000123 50.16225052 [12080] Command “BuildApp” handled by First Responder handled command
00000124 50.99842453 [11956] C:\Program Files\Xojo\Xojo 2018r4\Xojo.exe
00000125 50.99845505 [11956]
00000126 51.99951172 [11956] C:\Program Files\Xojo\Xojo 2018r4\Xojo.exe[/quote]

Greg_O_Lone · February 15, 2019, 9:32am

Just FYI Error 740 may just mean that the linker couldnt be launched.

http://windows-exe-errors.com/windows-error-740-the-requested-operation-requires-elevation/

Aditya_Nugraha · February 15, 2019, 10:28am

Dohhh, forgot that i have set lld.exe run as administrator in the lld.exe properties. Newest intel microcode in the bios with the same linker error :

[quote]Linking Executable
C:\Program Files\Xojo\Xojo 2018r4\Xojo Resources\Win32\lld.exe: error: C:\Users\echelon\AppData\Local\Temp\xojo scratch 5320\ChinookARGen [974F2B33]\Windows_x86_64\/Data.o: The file was not recognized as a valid object file[/quote]

And as always turning off Hyper-Threading fix it. I hope that there will be real fixes from xojo part.

Aditya_Nugraha · May 12, 2019, 4:51pm

I have tried contacting Intel supports but they mentioned that this is a specific(Xojo) software issue rather than Hardware issue or fixable by Intel or Asus, is it possible for Xojo team to fix it?.

Here is Intel’s reply :

Quoted from Intel’s Tech support reply :

Hi Mr. Aditya,

Good Morning!

We are writing to provide you with an update on your request. Thank you for patiently waiting for our update. After a long deliberation of your case, we regretfully inform you that, as much as we would like to help you, our engineers found out that the issue that you are experiencing compiling code with Xojo appears to be a known issue with the said program supporting multiple cores. You can find more information on the known issue on this blog on the Xojo website. You can open this link for reference: Supporting Multiple Cores – Xojo Programming Blog**. Because of this finding, we regretfully will not reproduce the issue since this appears to be a software incompatibility or limitation and it is beyond our support and we are strongly recommending for you to get in touch with Xojo again to ask for help to run the software or you can run the software while hyperthreading is enabled.

** Links to third party sites and references to third party trademarks are provided for convenience and illustrative purposes only. Unless explicitly stated, Intel® is not responsible for the contents of such links, and no third party endorsement of Intel® or any of its products is implied.

We hope that the above statement help clarify the issue. Because of this, we will go ahead and close the case. Thank you for finding time to read this email.

Have a nice day!

anon20074439 · May 12, 2019, 4:58pm

Looks like you got the brush off, that post no way reflects the issue you’re experiencing, I’d ask that it be escalated to someone that just doesn’t google the answer.

Aditya_Nugraha · May 12, 2019, 5:08pm

That screenshot is only minuscule of my communication with Intel, the so called Intel’s support already communication back and forth with planned Intel’s engineer supports. I kinda doubtful using Intel again as so-called Intel’s engineer cannot differentiate between Xojo’s compiler toolchain and compiled Xojo codes/apps . Did the Intel’s engineer or support is just being lazy or just the foolishness or Freshly graduated ‘engineer’ or support.

I will retry to contacting them again.

anon20074439 · May 12, 2019, 9:10pm

I can’t remember if you’ve tried this. Grab some free virtual machine software like virtual box and run a free Windows 10 ie test vm then give the build that fails a try and see if it works in the vm. I’d be interested if know if that works or not.

Aditya_Nugraha · June 15, 2019, 10:44pm

@
Just got the time to test Xojo in the virtual machine but it working flawlessly in vmware, and also i have tried to re-contacting intel but they mentioned the same reply as before and closed the report.

I think what intel means is the problem is not from the Xojo’s x64 llvm flavour toolchain but it’s from the Xojo IDE itself since it’s being made and compiled by the Xojo compiler itself, some how there is an edge case Xojo IDE not properly invoking “HoudiniAssistant64.exe”, it confirm my finding from monitoring “Xojo.exe” with Process Monitor software, there are some/a object files not properly created because of Xojo IDE (Xojo.exe) not invoking them.

What i have tried also replacing the lld.exe (Xojo’s linker?) with the one from LLVM official site (from version 6.0.0, up-to version 8.0.0, and nightly build), all of them failed to linked the corrupted object files, so we can negate both HoudiniAssistant64.exe (Xojo’s 64 bit windows compiler) and lld (Xojo’s linker) from having anything to do with those corrupted object files.

I bet my money that there are some race conditions in Xojo IDE (Xojo.exe) when spawning/invoking the Xojo’s linker and compiler.

In-case if it’s useful my CPU detected by HoudiniAssistant64.exe as :

[quote]HoudiniAssistant64.exe -version
LLVM (http://llvm.org/):
LLVM version 6.0.0
DEBUG build.
Default target: x86_64-pc-windows-msvc
Host CPU: skylake-avx512[/quote]

anon20074439 · June 27, 2019, 11:35am

First rule of pre-release is we can’t talk about pre-release, but all I wanted to say was:

Nice one all those involved, @Xojo, I’d be interested for some info on this when/if you can.

@Aditya Nugraha