[XFCE 0000040]: crash on double find

[xfce-bugs at xfce.org]

The following bug has been RESOLVED.
=======================================================================
http://bugs.xfce.org/view_bug_page.php?f_id=0000040
=======================================================================
Reporter:                   edscott
Handler:                    edscott
=======================================================================
Project:                    XFCE
Bug ID:                     0000040
Category:                   xffm
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     resolved
Resolution:                 fixed
=======================================================================
Date Submitted:             2003-12-10 20:50 GMT
Last Modified:              2003-12-11 01:48 GMT
=======================================================================
Summary:                    crash on double find
Description: 
do a find with path set to "/", and empty "filter" and "containing"
entries. The process will reached 64 results and stop. Repeat the find.
Crash (segv)

It seems like the automatic abort on reaching results limit might be
crooked some place.

=======================================================================

-----------------------------------------------------------------------
 edscott - 2003-12-10 20:52 GMT 
-----------------------------------------------------------------------
only 4.1 branch affected. So the bug might be in libs/tubo.c

-----------------------------------------------------------------------
 edscott - 2003-12-11 01:48 GMT 
-----------------------------------------------------------------------
A race condition existed because the function called when child finished
was being force called before child could terminate (race). The race is
removed and the function is called properly and the crash no longer
occurs. The waitpid() call was also missing the  WIFSIGNALED(status) test.
So the bug seems fixed now.