December 10, 2024

Xilinx Zynq - Vivado 2022.2 - bug with Fedora

It is not clear if this can be called a bug or just what to call it, but suddenly I am unable to start vivado.

I am still running 2022.2, thinking that it will be work to upgrade and why not avoid that for as long a possible, but today I tried to start Vivado and encountered: 

****** Vivado v2022.2 (64-bit)
  **** SW Build 3671981 on Fri Oct 14 04:59:54 MDT 2022
  **** IP Build 3669848 on Fri Oct 14 08:30:02 MDT 2022
    ** Copyright 1986-2022 Xilinx, Inc. All Rights Reserved.

Abnormal program termination (11)
Please check '/u1/home/tom/vivado/hs_err_pid786019.log' for details
segfault in /tools/Xilinx/Vivado/2022.2/bin/unwrapped/lnx64.o/vivado -exec vivado, exiting...
The log it suggests shows what looks like traceback with entries like this: 
Stack:
/lib64/libc.so.6(+0x19dd0) [0x7f9153825dd0]
/lib64/ld-linux-x86-64.so.2(+0xdda4) [0x7f91558dada4]
/lib64/ld-linux-x86-64.so.2(+0xc086) [0x7f91558d9086]
/lib64/ld-linux-x86-64.so.2(_dl_catch_exception+0xa3) [0x7f91558ce523]
/lib64/ld-linux-x86-64.so.2(+0xb520) [0x7f91558d8520]
/lib64/ld-linux-x86-64.so.2(_dl_catch_exception+0xa3) [0x7f91558ce523]
/lib64/ld-linux-x86-64.so.2(+0xb984) [0x7f91558d8984]
/lib64/libc.so.6(+0x6c8b4) [0x7f91538788b4]
/lib64/ld-linux-x86-64.so.2(_dl_catch_exception+0xa3) [0x7f91558ce523]
/lib64/ld-linux-x86-64.so.2(+0x1679) [0x7f91558ce679]
/lib64/libc.so.6(+0x6c3a3) [0x7f91538783a3]
/lib64/libc.so.6(dlopen+0x6f) [0x7f915387896f]
/tools/Xilinx/Vivado/2022.2/lib/lnx64.o/libtcl8.5.so(+0xddf50) [0x7f914e6ddf50]
My guess is that a recent version of glibc has rolled around and is the culprit. I am running Fedora 41 and up until today have been able to run Vivado without a problem. My dnf logs show glibc-common-0:2.40-12.fc41.x86_64 dropping in on 12-8-2024. Prior to that I had 2.40-3. Here is a discussion: My glibc version is not the glibc-2.28-251 that is mentioned for RHEL, but version numbers may be different for RHEL and Fedora. Note that I get the segfault when I start vivado, not on exit.

Downgrade

As an experiment: 
dnf downgrade glibc
( this takes me from 2.40-13 back to 2.40-3 )
This is easy enough, but does not seem to fix the problem.

I reboot, and after the reboot I can start vivado!

I type "dnf update" which brings back the latest glibc. And now I can start up vivado without a problem.

So it seems like the reboot fixed things, which is bad and weird.

Feedback? Questions? Drop me a line!

Tom's Computer Info / [email protected]