Various defects

[GoogleCodeExporter]

I observed a couple of spurious errors when running the unyaffs2 tools on 
target:

1) spurious crashes that disappeared when running under strace/gdb.
Using a coredump and valgrind I traced these back to the use  of 
list_for_each_entry() where list_for_each_entry_safe is required (see 
unyaffs2_objtable_exit and unyaffs2_specfile_exit() )

2) when running from a script using 2 '-f <file>' options the program would 
indicate that it did not find the 2 files, while running the exact same command 
from the shell ran fine.
It wasn't untill I checked compiler warnings that I found that a variable is 
not being initialized before use: see "off_t offset" in unyaffs2_scan_img() in 
case MMAP is used.

Original issue reported on code.google.com by HIGH...@gmail.com on 5 Sep 2011 at 2:26

[GoogleCodeExporter]

Original comment by penguin.lin on 13 Sep 2011 at 1:41

• Changed state: Accepted

[GoogleCodeExporter]

This issue should be fixed in the latest version.
I will close it when next minor release.

Original comment by penguin.lin on 1 Nov 2011 at 2:34

[GoogleCodeExporter]

Original comment by penguin.lin on 18 Nov 2011 at 7:11

• Changed state: Fixed