Description of problem: I accidentally built with the wrong --prefix arg, and then ran ncftool from the source directory, so it was trying to load stylesheets from /usr/local where they did not exist. When doing this valgrind reporting an invalid memory access I/O warning : failed to load external entity "/usr/local/share/netcf/xml/initscripts-get.xsl" error xsltParseStylesheetFile : cannot parse /usr/local/share/netcf/xml/initscripts-get.xsl I/O warning : failed to load external entity "/usr/local/share/netcf/xml/initscripts-put.xsl" error xsltParseStylesheetFile : cannot parse /usr/local/share/netcf/xml/initscripts-put.xsl I/O warning : failed to load external entity "/usr/local/share/netcf/xml/interface.rng" ==28730== Invalid read of size 4 ==28730== at 0x40127B6: remove_augeas_xfm_table (dutil.c:106) ==28730== by 0x4010617: bridge_physdevs (drv_initscripts.c:464) ==28730== by 0x401071B: drv_init (drv_initscripts.c:488) ==28730== by 0x400E401: ncf_init (netcf.c:98) ==28730== by 0x804A335: main (ncftool.c:755) ==28730== Address 0x404795c is 0 bytes after a block of size 4 alloc'd ==28730== at 0x4004E5C: calloc (vg_replace_malloc.c:397) ==28730== by 0x40147D1: safe_alloc_alloc_n (safe-alloc.c:82) ==28730== by 0x4012680: add_augeas_xfm_table (dutil.c:76) ==28730== by 0x401069F: drv_init (drv_initscripts.c:478) ==28730== by 0x400E401: ncf_init (netcf.c:98) ==28730== by 0x804A335: main (ncftool.c:755) ncftool> Version-Release number of selected component (if applicable): netcf-0.1.2-1.fc13.i386 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I'm not sure why this bug didn't show up in any lists up until now. While at least part of the code creating this problem has been removed in netcf-0.1.7 (all the iptables stuff to add the bridge rule), it still should be checked, so I'm moving the release to F14 so I'll be reminded to check it out.
(Doing some housekeeping...) I just built netcf-0.1.7 from sources with --prefix=/usr/local and ran the resulting ncftool under valgrind. valgrind didn't report any invalid memory accesses, and ncftool existed saying that it was unable to initialize (as expected). It appears that the code causing this problem has been removed/fixed.