SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The "worst" one is that /usr/lib{,64}/libgcc_s.so.1 mentioned by me in another thread.
Insert "the more you know!" gif here. My brain sure wouldn't have gone to gcc as the culprit. My thought process would've been that which was changed, and gcc wouldn't have registered since nothing that's crashing was compiled against/with it.
So, are there now a whole bunch of items that will need to be rebuilt with gcc14 ?
Well, technically... ALL.
My bet is that on a particular town from Minnesota the lights started to flicker erratically, because our BDFL powered up his entire computers fleet for a really Mass Rebuild.
Let's hope that no compile errors will happen, thought...
Last edited by LuckyCyborg; 05-14-2024 at 07:58 PM.
Well, I'm happy to report that things have gone back to normal.
I tried to revert first to gcc 13.2. System still messed.
Reverted the kernel to 6.6.30, and only then, with kernel 6.6.30 and gcc-13.2, I got things back to normal.
Considering reports from willy, I think that the culprit may have been the newest kernel; not in itself, but because it might have been built with gcc-14.
Will keep investigating. Thanks everyone for their advice.
I hope not many because 6.9's been pretty good for me.
I think the kernel itself it's good; what caused the instability might have been that it had been built with that bugged gcc. Just a speculation but at least it makes sense.
I think the kernel itself it's good; what caused the instability might have been that it had been built with that bugged gcc. Just a speculation but at least it makes sense.
I played about an hour of Diablo IV after dinner, then loaded palworld again, just to see if it would crash with the issue I had in 6.6.30. (Everything was fine. I did have a memory leak, but Diablo IV is horrible in that regard.) Youtube videos while playing vampire survivors, and everything seems OK...then again neither are very demanding nor use qt.
As stated by Ponce, some of the sources have been patched to work with GCC 14, but maybe not all of them need to be rebuilt, so that's why Patrick didn't do a mass rebuild. At least the sources have been tested to work with GCC 14, but only at build time. We still have runtime issue, like what we had right now
As stated by Ponce, some of the sources have been patched to work with GCC 14, but maybe not all of them need to be rebuilt, so that's why Patrick didn't do a mass rebuild. At least the sources have been tested to work with GCC 14, but only at build time. We still have runtime issue, like what we had right now
It is usually better to get things ready to rebuild, but to rebuild as little as possible, in case of buggy gcc.
When this happens it usually means that a binary program has been compiled with flags allowing the use of instructions that is lacking on your CPU. Examples of such instructions might be SSE and AVX in different generations. Having instructions not supported by your CPU in the executable program itself or some dynamic library used by the program will cause a crash with that error message when trying to use that instruction.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
My brain sure wouldn't have gone to gcc as the culprit. My thought process would've been that which was changed, and gcc wouldn't have registered since nothing that's crashing was compiled against/with it.
