Package: libgc Severity: important When libgc is run on 2.6 arm kernels, the first call to GC_malloc causes a SIGSEGV, presumably triggered by the different VM layout in 2.4. This happens on sarge as well as on unstable.
A fix for the problem is to use the LINUX_STACKBOTTOM check instead of HEURISTIC1 if __ARM__ is defined, which is how this issue has been fixed in upstream 6.6. Whether this change breaks 2.4 remains to be tested. -- System Information: Debian Release: testing/unstable APT prefers stable APT policy: (500, 'stable') Architecture: armeb (armv5teb) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
