On Mon, 2006-12-18 at 04:59 +0100, Leszek Koltunski wrote: > #0 0xf7e8306c in ?? () from /usr/lib/libfontconfig.so.1 > #1 0xf7e84fc4 in FcDirCacheOpenFile (cache_file=<value optimized out>, > file_stat=0xffa541e4) at /usr/include/sys/stat.h:380
Ok, I'm mystified. The stack trace (even with -O) appears clean, and terminates with a call to fstat, which is segfaulting. The only memory referenced by that call is a struct stat object, which is allocated on the stack in the calling function. I can't think of what else we can do to figure this bug out; about the only additional information we could get would be to rebuild the library without optimization to make sure things are crashing precisely where they appear to be crashing. If I were able to, I'd put a breakpoint in FcDirCacheOpenFile and make sure the struct stat were accessible before stepping into the fstat function. Would that it failed on someone else's machine... -- [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
