Hey all,

I had a quick look in the mail archive and didn't see anything on this, but
it's not impossible others will come across/have come across the same issue
I've encountered, so figured I'd potentially save some people future
frustrations and heart attacks.

There's an issue with later versions of Matlab (R2021a and up) on older
versions of Ubuntu (18.04 and down) where opening Simulink intermittently
causes Matlab to crash with some variation of the following error:

*Inconsistency detected by ld.so: ../elf/dl-tls.c: 517:
_dl_allocate_tls_init: Assertion `listp != NULL' failed!*

This is due to a bug in the glibc library present on older versions of
Linux distros that doesn't play nicely with the new way Matlab does some
things. Fortunately, Mathworks doth provide an answer. Not so fortunately,
their official answer is "upgrade to a newer operating system with a
version of glibc that doesn't have this bug". Lol.

But they also kindly provide a solution
<https://github.com/mathworks/build-glibc-bz-19329-patch> for those of us
who can't just upgrade; an unofficial patch of the glibc libraries that
fixes this bug for various OS versions. This of course comes with the major
caveat that modifying system files is done at your own risk - all processes
in the OS share glibc, so the patch will affect your whole system, not just
Matlab, and this could cause weirdness.

So if you find yourself in the same position I was yesterday, wondering if
you should risk it all just for Simulink - I'm happy to report that I
applied this patch, the universe did not end and nothing on my machine
*seems* to be broken. Great success.

That is all,
Morag

-- 
You received this message because you are subscribed to the Google Groups 
"[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0Tc-dJ0AUnC21S5oTP-pRXyhMC_Ld%2B8KyQ31NuSFZ7HfkQ%40mail.gmail.com.

Reply via email to