From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile-sdl@gnu.org
Cc: 22020@debbugs.gnu.org
Subject: bug#22020: Guile-SDL 0.5.2 test failure i686-linux-gnu
Date: Fri, 05 Feb 2016 14:13:04 +0100 [thread overview]
Message-ID: <87lh6zl2qn.fsf@gnu.org> (raw)
In-Reply-To: <1448577083.28162.7.camel@openmailbox.org>
[-- Attachment #1: Type: text/plain, Size: 175 bytes --]
Hi!
I’m not seeing the message below at
<http://lists.gnu.org/archive/html/bug-guile-sdl/>, so resending it.
(This is from <http://bugs.gnu.org/22020>.)
Ludo’.
[-- Attachment #2: Type: message/rfc822, Size: 5995 bytes --]
From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile-sdl@gnu.org, 22020@debbugs.gnu.org
Cc: 22020@debbugs.gnu.org
Subject: bug#22020: Guile-SDL 0.5.2 test failure i686-linux-gnu
Date: Sun, 29 Nov 2015 12:49:59 +0100
Message-ID: <874mg5m3dk.fsf@gnu.org>
Hello!
On GNU Guix, we’re seeing one 100% reproducible test failure on
i686-linux-gnu:
--8<---------------cut here---------------start------------->8---
/gnu/store/isxqjfaglyfsbcv75y8qbqbph8v28ykr-bash-4.3.39/bin/bash: line 5: 838 Segmentation fault (core dumped) HAVE_TTF=1 HAVE_MIXER=0 sh zow ${dir}$tst
FAIL: gfx.scm
_FontTransOpen: Unable to Parse address ${prefix}/share/fonts/X11/misc/
_FontTransOpen: Unable to Parse address ${prefix}/share/fonts/X11/TTF/
_FontTransOpen: Unable to Parse address ${prefix}/share/fonts/X11/OTF/
_FontTransOpen: Unable to Parse address ${prefix}/share/fonts/X11/Type1/
_FontTransOpen: Unable to Parse address ${prefix}/share/fonts/X11/100dpi/
_FontTransOpen: Unable to Parse address ${prefix}/share/fonts/X11/75dpi/
_FontTransOpen: Unable to Parse address ${prefix}/share/fonts/X11/misc/
_FontTransOpen: Unable to Parse address ${prefix}/share/fonts/X11/TTF/
_FontTransOpen: Unable to Parse address ${prefix}/share/fonts/X11/OTF/
_FontTransOpen: Unable to Parse address ${prefix}/share/fonts/X11/Type1/
_FontTransOpen: Unable to Parse address ${prefix}/share/fonts/X11/100dpi/
_FontTransOpen: Unable to Parse address ${prefix}/share/fonts/X11/75dpi/
PASS: fading.scm
======================================
1 of 9 tests failed
(2 tests were not run)
Please report to bug-guile-sdl@gnu.org
======================================
--8<---------------cut here---------------end--------------->8---
(Note that we run tests with the Xvfb server. See
<http://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/sdl.scm#n303>.)
The backtrace is mildly informative:
--8<---------------cut here---------------start------------->8---
$ gdb $(type -P guile) core
GNU gdb (GDB) 7.10
[...]
(gdb) bt
#0 0xf4d98130 in SDL_imageFilterSubByteMMX (Src1=0x5d <error: Cannot access memory at address 0x5d>, Dest=0xffb429c8 "]",
SrcLength=4107944472, C=152 '\230') at SDL_imageFilter.c:2185
#1 0x09cfd470 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
--8<---------------cut here---------------end--------------->8---
That SrcLength is so high suggests it might be an integer overflow.
This is with SDL_image 1.2.12.
To reproduce with Guix, run:
guix build guile-sdl -s i686-linux --keep-failed
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-02-05 13:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 22:31 bug#22020: guile-sdl-0.5.2 fails to install on i686 Luis Felipe López Acevedo
2015-11-29 11:49 ` bug#22020: Guile-SDL 0.5.2 test failure i686-linux-gnu Ludovic Courtès
2016-02-05 13:13 ` Ludovic Courtès [this message]
2020-05-14 17:55 ` bug#22020: guile-sdl-0.5.2 fails to install on i686 Ricardo Wurmus
2020-05-17 12:05 ` Efraim Flashner
2022-06-19 22:59 ` bug#22020: [PATCH] gnu: guile-sdl: Update to 0.6.1 Thiago Jung Bauermann via Bug reports for GNU Guix
2022-09-01 13:07 ` Efraim Flashner
2022-09-03 2:58 ` Thiago Jung Bauermann via Bug reports for GNU Guix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lh6zl2qn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=22020@debbugs.gnu.org \
--cc=bug-guile-sdl@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).