Update of bug #46670 (project findutils):
Assigned to: None => jay
_______________________________________________________
Follow-up Comment #1:
Thanks for the bug report. The symptoms you're describing certainly sound
like a bug.
Your bug report didn't indicate which version you found this in. If the
affected version is not 4.5.10 or later, could you download version 4.5.14
from http://alpha.gnu.org/pub/gnu/findutils and try to reproduce the problem.
When you build from source two find executables are created: "find" and
"oldfind". It would also be useful to know if the problem manifests the same
way in both.
Supposing the problem is reproducible though, on the basis of the limited
information we have so far, it's hard to discern what might be responsible.
There are a few ways to get more information. The simplest is to use the -D
option, like this:
find -D search,stat,rates / -uid 1000 -print
(I'm also curious to see if you get the same behaviour if you add -depth).
A system call trace via e.g. strace (or function call trace via ltrace) might
also be helpful but they also create such large outputs that unsurprisingly
it's not always easy to locate the spot where things went wrong.
Certainly, there are few places where the find executable directly calls exit
(for --help, --version, -quit, in child processes). So evidence -
specifically a backrrace - from a debugger may help. In case you're not
familiar with using a debugger, here is an example:
$ gdb --quiet find
Reading symbols from find...(no debugging symbols found)...done.
(gdb) break _exit
Breakpoint 1 at 0x402770
(gdb) break exit
Breakpoint 2 at 0x402ea0
(gdb) run /storage -uid 1000 -print
Starting program: /usr/bin/find /storage -uid 1000 -print
/usr/bin/find: `/storage': No such file or directory
Breakpoint 2, __GI_exit (status=1) at exit.c:104
104 exit.c: No such file or directory.
(gdb) backtrace
#0 __GI_exit (status=1) at exit.c:104
#1 0x00007ffff7753b4c in __libc_start_main (main=0x402f70, argc=5,
argv=0x7fffffffe8a8,
init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>,
stack_end=0x7fffffffe898)
at libc-start.c:321
#2 0x000000000040316f in ?? ()
(gdb) quit
A debugging session is active.
Inferior 1 [process 3060] will be killed.
Quit anyway? (y or n) y
$
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?46670>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
