Ferenc Wágner <wf...@niif.hu> writes: > I've been looking into this for quite some time.
Great, thanks! > I created an x32 build environment, and the build finished without any > problem, I failed to reproduce the segfault. If you could extract a > core dump or at least a backtrace from the buildd, I'd gladly check it > out. To be clear, I'm not a porter or buildd maintainer, just a regular DD who's found that architecture-specific build failures sometimes slip through the cracks and likes to help ensure they don't. It looks like valgrind doesn't yet support x32, but I suppose you could see if building with -fsanitize=address catches anything. (Also, I'm not sure autobuilders retain any details they don't publish anyway.) -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu