[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#148650: xfs: SEGV if catalogue line omitted from config file



Version: 1:1.0.6-1

I can confirm this with version 1:1.0.6-1.  I just did a test run with
valgrind, and this is the output when it crashes.  Did not have time
to rebuild xfs with debug symbols.  Sorry about that.

# valgrind xfs
==14613== Memcheck, a memory error detector.
==14613== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==14613== Using LibVEX rev 1804, a library for dynamic binary translation.
==14613== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==14613== Using valgrind-3.3.0-Debian, a dynamic binary instrumentation framework.
==14613== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==14613== For more details, rerun with: -v
==14613==
==14613== Invalid read of size 1
==14613==    at 0x40239D8: strlen (mc_replace_strmem.c:242)
==14613==    by 0x8051873: (within /usr/bin/xfs)
==14613==    by 0x8054FD9: (within /usr/bin/xfs)
==14613==    by 0x805268E: (within /usr/bin/xfs)
==14613==    by 0x40CA44F: (below main) (libc-start.c:222)
==14613==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==14613==
==14613== Process terminating with default action of signal 11 (SIGSEGV)
==14613==  Access not within mapped region at address 0x0
==14613==    at 0x40239D8: strlen (mc_replace_strmem.c:242)
==14613==    by 0x8051873: (within /usr/bin/xfs)
==14613==    by 0x8054FD9: (within /usr/bin/xfs)
==14613==    by 0x805268E: (within /usr/bin/xfs)
==14613==    by 0x40CA44F: (below main) (libc-start.c:222)
==14613==
==14613== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 23 from 1)
==14613== malloc/free: in use at exit: 4,686 bytes in 67 blocks.
==14613== malloc/free: 101 allocs, 34 frees, 40,458 bytes allocated.
==14613== For counts of detected errors, rerun with: -v
==14613== searching for pointers to 67 not-freed blocks.
==14613== checked 168,548 bytes.
==14613==
==14613== LEAK SUMMARY:
==14613==    definitely lost: 0 bytes in 0 blocks.
==14613==      possibly lost: 0 bytes in 0 blocks.
==14613==    still reachable: 4,686 bytes in 67 blocks.
==14613==         suppressed: 0 bytes in 0 blocks.
==14613== Rerun with --leak-check=full to see details of leaked memory.
Segmentation fault
#

Happy hacking,
-- 
Petter Reinholdtsen



Reply to: