> Hello, >> If this is the case, then there could be a bug in Squashfs 3.0. > It can also be caused by unionfs, which could be unable to handle some > squashfs > 3 feature properly. > I saw this already in the past, sometimes unionfs needs some special handling > for special filesystems, > for example for NFS.
Enable the "compile with frame pointers" thing in the kernel, which might could 'fix' the impossible stack trace. Jan Engelhardt -- _______________________________________________ unionfs mailing list [email protected] http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
