Re: find command trigger coredump

[Bernhard Voelker]

On 2020-04-16 06:03, Paul Eggert wrote:
> I worked around the bug by removing that optimization from Gnulib fts.c, by 
> installing the attached patch. I expect that this optimization is obsolete 
> nowadays, as XFS is now working and ReiserFS is either working, or is so 
> unpopular that high performance for du and find is not that important for it.

Thanks for the patch.
I installed it in my local findutils tree, but find still crashes:

(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007f1fea53f53d in __GI_abort () at abort.c:79
#2  0x00000000004039f5 in leave_dir (fts=<optimized out>, fts=<optimized out>, 
ent=<optimized out>) at fts-cycle.c:136
#3  leave_dir (ent=<optimized out>, fts=<optimized out>, fts=<optimized out>) 
at fts-cycle.c:125
#4  0x000000000041feef in fts_build (sp=sp@entry=0x1b33a50, type=type@entry=3) 
at fts.c:1361
#5  0x0000000000420a5d in rpl_fts_read (sp=sp@entry=0x1b33a50) at fts.c:940
#6  0x0000000000403eb3 in find (arg=arg@entry=0x7fff2c1b36c9 "/opt") at 
ftsfind.c:561
#7  0x0000000000403b3a in process_all_startpoints (argv=<optimized out>, 
argc=<optimized out>) at ftsfind.c:625
#8  main (argc=<optimized out>, argv=<optimized out>) at ftsfind.c:734

It seems the likeliness of the crash is almost the same, unfortunately.

Did it fix the crash for you (maybe in du(1))?

Have a nice day,
Berny