![]() ![]() One more thing: I'm not compiling python packages, so changing of compilator options od 'myapp' (python package) is not an option. ![]() Also I'm using other Python packages that requires glibc 2.14 to work, so I'm aware which version of glibc I'm using at the moment.Īlso if there were some kind of mismatch in libraries then it shouldn't work at all (.probably).Īlso as I mentioned at the beginning I've noticed that the problem is related to memory (still not sure what is happening with 32 GB of RAM machine). The problem is that the segmentation fault shows up on random machines while only using new glibc. In my case Python works with additional glibc. Thanks, but probabaly not the problem with Multiple glibc libraries on a single host. So, we can see the newest version of glibc is 2.1.2, we need to upgrade glibc to 2.14. Right now I found workaround which were the new python packages from anaconda that are compatibile with glibc 2.12 (become available few days ago) and packages' dependencies also does not require newer Russian: Update glibc library version to 2.14 in CentOS6. However problem still exist on production machine with 32 GB of RAM. I’m including them in hopes that the search engine bots will bring you to this blog so that you can save some. After some more investigating I've noticed that assigning more memory to lab machines (from 2/4 GB to 6 and more) make the segmentation fault error to go away. Pitfall 2: In your research you may have come across the following errors below.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |