Your message dated Wed, 09 Jan 2013 13:44:29 -0800 with message-id <[email protected]> and subject line SBCL Bus Error has caused the Debian Bug report #572967, regarding Core dump with bus error to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 572967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572967 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: sbcl Version: 1:1.0.34.0-1 Severity: grave After I installed the latest SBCL, I couldn't run it without getting a bus error. Here's the output of gdb with the core dump: -------------8<-----------------8<-------------------------------------- Reading symbols from /usr/bin/sbcl...(no debugging symbols found)...done. warning: Can't read pathname for load map: Erreur d'entrée/sortie. Reading symbols from /lib/libdl.so.2...Reading symbols from /usr/lib/debug/lib/libdl-2.10.2.so...done. (no debugging symbols found)...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/libpthread.so.0...Reading symbols from /usr/lib/debug/lib/libpthread-2.10.2.so...done. (no debugging symbols found)...done. Loaded symbols for /lib/libpthread.so.0 Reading symbols from /lib/libm.so.6...Reading symbols from /usr/lib/debug/lib/libm-2.10.2.so...done. (no debugging symbols found)...done. Loaded symbols for /lib/libm.so.6 Reading symbols from /lib/libc.so.6...Reading symbols from /usr/lib/debug/lib/libc-2.10.2.so...done. (no debugging symbols found)...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2...Reading symbols from /usr/lib/debug/lib/ld-2.10.2.so...done. (no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Core was generated by `sbcl'. Program terminated with signal 7, Bus error. #0 0x00000010005249e0 in ?? () (gdb) bt #0 0x00000010005249e0 in ?? () #1 0x00007ffff51a0c80 in ?? () #2 0x0000000000000000 in ?? () (gdb) -------------8<-----------------8<-------------------------------------- -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (900, 'stable'), (600, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sbcl depends on: ii common-lisp-controller 7.1 Common Lisp source and compiler ma ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib Versions of packages sbcl recommends: ii binfmt-support 1.2.17 Support for extra binary formats Versions of packages sbcl suggests: ii sbcl-doc 1:1.0.25.0-1 Documentation for Steel Bank Commo ii sbcl-source 1:1.0.25.0-1 Source code files for SBCL ii slime 1:20100220-2 Superior LISP Interaction Mode for -- no debconf information
--- End Message ---
--- Begin Message ---Hi! This bug is not marked unreproducible for almost 2 years. I'll close it for now. If anyone is still experiencing bus errors please reopen / report a new bug. Would be great to get some more information about what kind of system this is happening on (there seem to be some problems with OpenVZ and things like that: #559954). Regards Christoph
--- End Message ---
_______________________________________________ pkg-common-lisp-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-common-lisp-devel
