problems with non-ascii chars in dirname with sb-posix build and run-sbcl.sh

Bug #601576 reported by Bernd Beuster
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
SBCL
Triaged
Medium
Unassigned

Bug Description

Test SB-POSIX-TESTS::READDIR.1 failed
Form: (LET ((SB-POSIX-TESTS::DIR (SB-POSIX:OPENDIR "/")))
        (UNWIND-PROTECT
            (BLOCK SB-POSIX-TESTS::DIR-LOOP
              (LOOP SB-POSIX-TESTS::FOR SB-POSIX-TESTS::DIRENT = (SB-POSIX:READDIR
                                                                  SB-POSIX-TESTS::DIR)
                    SB-POSIX-TESTS::UNTIL (NULL-ALIEN SB-POSIX-TESTS::DIRENT)
                    WHEN (NOT
                          (STRINGP
                           (SB-POSIX:DIRENT-NAME SB-POSIX-TESTS::DIRENT)))
                    DO (RETURN-FROM SB-POSIX-TESTS::DIR-LOOP NIL)
                    SB-POSIX-TESTS::FINALLY (RETURN T)))
          (SB-POSIX:CLOSEDIR SB-POSIX-TESTS::DIR)))
Expected value: T
Actual value: #<SB-INT:C-STRING-DECODING-ERROR {1002D6CF51}>.
 SB-POSIX-TESTS::PWENT.1 SB-POSIX-TESTS::PWENT.2
 SB-POSIX-TESTS::PWENT.NON-EXISTING SB-POSIX-TESTS::GRENT.1
 SB-POSIX-TESTS::GRENT.2 SB-POSIX-TESTS::GRENT.NON-EXISTING
 SB-POSIX-TESTS::TIME.1 SB-POSIX-TESTS::UTIMES.1 SB-POSIX-TESTS::READLINK.1
 SB-POSIX-TESTS::READLINK.2 SB-POSIX-TESTS::READLINK.ERROR.1
 SB-POSIX-TESTS::READLINK.ERROR.2 SB-POSIX-TESTS::READLINK.ERROR.3
 SB-POSIX-TESTS::READLINK.ERROR.4 SB-POSIX-TESTS::READLINK.ERROR.5
 SB-POSIX-TESTS::READLINK.ERROR.6 SB-POSIX-TESTS::READLINK.ERROR.7
 SB-POSIX-TESTS::GETCWD.1 SB-POSIX-TESTS::MKSTEMP.1 SB-POSIX-TESTS::MKDTEMP.1
 SB-POSIX-TESTS::MKTEMP.1 SB-POSIX-TESTS::MKSTEMP.NULL-TERMINATE
 SB-POSIX-TESTS::ENVSTUFF
1 out of 68 total tests failed: SB-POSIX-TESTS::READDIR.1.unhandled SIMPLE-ERROR in thread #<SB-THREAD:THREAD "initial thread" RUNN$
                                   {1002AE51D1}>:
  non-errno tests failed!

Revision history for this message
Bernd Beuster (bernd-beuster) wrote :
Revision history for this message
Bernd Beuster (bernd-beuster) wrote :

32-bit Kernel

flexo:~ bernd$ uname -a
Darwin flexo.fritz.box 10.4.0 Darwin Kernel Version 10.4.0: Fri Apr 23 18:28:53 PDT 2010; root:xnu-1504.7.4~1/RELEASE_I386 i386

Revision history for this message
Nikodemus Siivola (nikodemus) wrote :

Additional information:

Philippe Mechaï to sbcl-devel:

As already reported (see https://bugs.launchpad.net/sbcl/+bug/601576), sb-posix tests fail (at least on Mac OS X) when a folder name contains special characters (in my case a trademark sign).
The bug is still present in latest version from Git (v1.0.43.65). This is non blocking as I can disable the readdir test if I need to, but I thought it was worth mentioning.

Changed in sbcl:
assignee: nobody → Nikodemus Siivola (nikodemus)
Revision history for this message
Nikodemus Siivola (nikodemus) wrote :
Download full text (10.1 KiB)

Wow, this is pretty spectacular.

> LANG=C sh run-sbcl.sh
(running SBCL from: /Users/nikodemus/src/sbcl-öäå)
This is SBCL 1.0.43.75, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses. See the CREDITS and COPYING files in the
distribution for more information.
CORRUPTION WARNING in SBCL pid 45397(tid 140735072831232):
Memory fault at 152000 (pc=0x1000729b2f, sp=0x31ff490)
The integrity of this image is possibly compromised.
Continuing with fingers crossed.
CORRUPTION WARNING in SBCL pid 45397(tid 140735072831232):
Enabling blocked gc signals to allow returning to Lisp without risking
gc deadlocks. Since GC signals are only blocked in signal handlers when
they are not safe to interrupt at all, this is a pretty severe occurrence.

The integrity of this image is possibly compromised.
Continuing with fingers crossed.
CORRUPTION WARNING in SBCL pid 45397(tid 140735072831232):
Memory fault at 152000 (pc=0x100072aa3b, sp=0x31feef0)
The integrity of this image is possibly compromised.
Continuing with fingers crossed.
CORRUPTION WARNING in SBCL pid 45397(tid 140735072831232):
Memory fault at 152000 (pc=0x1000729b2f, sp=0x31fe530)
The integrity of this image is possibly compromised.
Continuing with fingers crossed.
CORRUPTION WARNING in SBCL pid 45397(tid 140735072831232):
Memory fault at 152000 (pc=0x100072aa3b, sp=0x31fdf90)
The integrity of this image is possibly compromised.
Continuing with fingers crossed.
CORRUPTION WARNING in SBCL pid 45397(tid 140735072831232):
Memory fault at 152000 (pc=0x1000729b2f, sp=0x31fd5d0)
The integrity of this image is possibly compromised.
Continuing with fingers crossed.
CORRUPTION WARNING in SBCL pid 45397(tid 140735072831232):
Memory fault at 152000 (pc=0x100072aa3b, sp=0x31fd030)
The integrity of this image is possibly compromised.
Continuing with fingers crossed.
CORRUPTION WARNING in SBCL pid 45397(tid 140735072831232):
Memory fault at 152000 (pc=0x1000729b2f, sp=0x31fc670)
The integrity of this image is possibly compromised.
Continuing with fingers crossed.
CORRUPTION WARNING in SBCL pid 45397(tid 140735072831232):
Memory fault at 152000 (pc=0x100072aa3b, sp=0x31fc0d0)
The integrity of this image is possibly compromised.
Continuing with fingers crossed.
CORRUPTION WARNING in SBCL pid 45397(tid 140735072831232):
Memory fault at 152000 (pc=0x1000729b2f, sp=0x31fb710)
The integrity of this image is possibly compromised.
Continuing with fingers crossed.
CORRUPTION WARNING in SBCL pid 45397(tid 140735072831232):
Memory fault at 152000 (pc=0x100072aa3b, sp=0x31fb170)
The integrity of this image is possibly compromised.
Continuing with fingers crossed.
CORRUPTION WARNING in SBCL pid 45397(tid 140735072831232):
Memory fault at 152000 (pc=0x1000729b2f, sp=0x31fa7b0)
The integrity of this image is possibly compromised.
Continuing with fingers crossed.
CORRUPTION WARNING in SBCL pid 45397(tid 140735072831232):
Memory fault at 152000 (pc=0x100072aa3b, sp=0x31fa210)
The integrity of this image is possibly compro...

Changed in sbcl:
status: New → In Progress
Changed in sbcl:
importance: Undecided → Medium
status: In Progress → Triaged
summary: - Build of sb-posix fails with 1.0.40 and MacOSX 10.6.4
+ problems with non-ascii chars in dirname with sb-posix build and run-
+ sbcl.sh
Revision history for this message
Nikodemus Siivola (nikodemus) wrote :

This doesn't make it all better, but at least allows SBCL to start up when the dirname contains non-ASCII characters.

https://github.com/nikodemus/SBCL/commit/78f303541c0b0a3ff324b4d5e1da7650e8311126

Changed in sbcl:
status: Triaged → In Progress
Revision history for this message
Nikodemus Siivola (nikodemus) wrote :

I think the right thing here look like this:

1. Implement UTF-8b.

2. Add *system-external-format*. Default on Windows is UCS-2, and UTF-8b everywhere else.

3. Use it for pathnames and environment variables.

Changed in sbcl:
assignee: Nikodemus Siivola (nikodemus) → nobody
status: In Progress → Triaged
Revision history for this message
Mark.Evenson (evenson-not-org) wrote :

Still an active problem on OS X, cf. <https://trac.macports.org/ticket/40980>.

Revision history for this message
Stas Boukarev (stassats) wrote :

I can't comment there, but if it's such an active problem, why can't they set LANG or LC_CTYPE to a proper value?

Revision history for this message
ciel (cielavenir) wrote :

Hi,

OSX (Japanese) has /ユーザ情報, which contains ENERGYSTAR.pdf. Other non-European OSX Installation are similar.
By the way, LANG=ja_JP.UTF-8, so it should be alright.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.