On Thu, Aug 14, 2008 at 05:57:20PM -0000, ingo wrote:
>
> Now to your recent request regarding the image:
> it still crashes on Hardy, see this output:
>
> # /sbin/e2fsck ./qnap-sdc3.img
> e2fsck 1.40.8 (13-Mar-2008)
> ./qnap-sdc3.img has unsupported feature(s):Segmentation fault (core dumped)
> [EMAIL PROTECTED]:/home/ingo/data/temp/QNAP-ext3+#
As I mentioned to you earlier, I can't reproduce the bug on my end.
The problem is the stack has been corrupted, so there's not much I can
do with the stack backtrace. Given what it has printed, it is almost
certainly in the call to e2p_feature2string --- but dumpe2fs calls
that, and without any problems on your system.
Because of where the segfault lies, it's before the newline is
printed, which localizes the code to precisely this region:
fprintf(stderr, _("%s has unsupported feature(s):"),
ctx->filesystem_name);
for (i=0; i <3; i++,mask++) {
for (j=0,m=1; j < 32; j++, m<<=1) {
if (*mask & m)
fprintf(stderr, " %s",
e2p_feature2string(i, m));
}
}
putc('\n', stderr);
... and e2p_feature2string doesn't call strlen() anywhere. So I'm
totally at a loss what's going on here. I've tried running valgrind
on the e2fsck 1.40.8 system, and have turned up nothing.
I guess something you can try is to see if valgrind turns up something
for you on your system. Failing that, if you are willing to build
e2fsprogs from sources, and then try to replicate the problem and run
it under gdb, we might get somewhere. Otherwise, I really don't know
what to tell you. It is a mystery what is going on here.
- Ted
--
e2fsck crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/257048
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
