>>>> "Jack" == Jack Twilley
<jmt(a)twilley.org> writes:
Jack> XEmacs does crash when I visit a PNG file, but that doesn't
Jack> tell me we've got a faulty library.
That makes plenty of sense, but: been there, done that. Upgrading
libpng (or perhaps simply rebuilding it with a newer toolchain) has
caused crashes on at least Solaris. Rebuild XEmacs, crash goes away
in those cases. We've seen the stack traces for those, it is pretty
clearly crashing inside of libpng, not in the glue code. Guessing
that it's the same for your crash is a bit of a stretch, but this is
very stable code (I don't think it has changed since XEmacs 20.4, and
it's basically the same in 21.4 and 21.5 as in 21.1), and we know that
libpng upgrades caused crashes on other similar platforms.
Jack> It's more likely to me that the glue code in XEmacs between
Jack> libpng and the app is at fault in that it's probably not
Jack> handling console-mode properly.
Well, that's what we're talking about, too. XEmacs was probably built
with an older header. When Steve says "dodgy library", what he means
is that libpng upgraded in a backwards incompatible way but is still
link-compatible. Boom!
SY> You obviously have reasons for not building your own XEmacs
SY> from source, but that may well be the quickest solution to
SY> your problem.
Jack> I'll do it as a last resort.
Have you rebuilt XEmacs from the port since the most recent upgrade of
libpng?
You _are_ going to have to rebuild, unless you can get somebody else to
do it for you. You cannot possibly solve a crash without rebuilding
(except by avoiding use of the "dangerous" feature).
--
Institute of Policy and Planning Sciences
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.