On Sam, 2005-09-03 at 10:35 +1000, Greg Schafer wrote: > Better still, we should just find the bug and fix it. Why pessimize the > whole of Util-linux just because of an intermittent bug in cfdisk? It's a > bad workaround IMHO. Surely someone who is able to reproduce the crash can > obtain a backtrace so we at least know where to start looking?
It's not as easy as it sounds. As it's very likely that it's a GCC optimization bug you can't really debug the compiled cfdisk as the generated code is wrong. The stack after the SEGV is completely destroyed, gdb doesn't help at all. What should really be done is trying to minimize the source code of cfdisk as much as possible while keeping the segfault, so we'd have a testcase to submit upstream resp. see whether it's already reported in gcc's bugzilla. Maybe it wouldn't be that unwise to test with current 4.0 (or maybe also 4.1) snapshot as it may already have been fixed. Will test that afterwards and maybe try to create a testcase. Regards, Jürg -- Jürg Billeter <[EMAIL PROTECTED]> -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
