This may be one more the dev list, but here goes anyway.
In testing my Java binding for TSK (soon to be released I promise!) I
came across weird errors when calling tsk_fs_dir_walk. I was under the
impression that if I wanted to halt the walk, no matter where in the
recursive process we are, I could call TSK_WALK_ERROR from the
callback. Yet looking at the code in fs_dir.c it appears that if the
callback returns TSK_WALK_ERROR, the central tsk_fs_dir_walk_lcl can
'reset the error' and continue. It appears that TSK_WALK_STOP will bail
the walk immediately. This behaviour doesn't seem to jive with the
public (web) explanations of the WALK_RET_ENUM.
Anyone care to comment?
Stuart
|