Hi, NeuroDebian Team account <[email protected]> writes:
> Package: libatlas3-base > Version: 3.8.4-8 > Severity: important > File: /usr/lib/atlas-base/atlas/libblas.so.3.0 > > Dear Maintainer, > > Today I have upgraded the system and I guess moved from my custom build of > atlas to Debian-provided and got my illops back: > > Program received signal SIGILL, Illegal instruction. > 0x00007ffff478e2fa in ATL_dJIK56x56x56TN56x56x0_a1_b0 () from > /usr/lib/libblas.so.3gf > (gdb) bt 2 full > #0 0x00007ffff478e2fa in ATL_dJIK56x56x56TN56x56x0_a1_b0 () from > /usr/lib/libblas.so.3gf > No symbol table info available. > #1 0x00007ffff486f546 in ATL_dprk_kmm () from /usr/lib/libblas.so.3gf > No symbol table info available. > (More stack frames follow...) Thanks for your report. So the atlas illops is not over, sigh… I think this is a different issue than the one you reported in #610196. Now the compiler flags are generic, so the problem must come from some explicit assembly code. This is not going to be easy to debug. I guess that your CPU is the same than the one given in #610196; if not please provide the right information. Also a full backtrace of the crash would be useful. As you have probably guessed, the workaround for your problem is to compile a custom atlas package, as explained in README.Debian. Best, -- .''`. Sébastien Villemot : :' : Debian Maintainer `. `' http://www.dynare.org/sebastien `- GPG Key: 4096R/381A7594
pgp93A8v1W5xb.pgp
Description: PGP signature
