On Tue, May 30, 2023 at 05:09:07PM -0400, Nick Black (Public gmail account)
wrote:
> I've been using plocate for many months on all my machines without problems.
> Recently, I get a coredump on any search, on all the machines on which I've
> tested. I've got a stack trace that points at do_search_file():
>
> Thread 1 (Thread 0x7f426c687740 (LWP 914015) "locate"):
> #0 __pthread_kill_implementation (threadid=<optimized out>,
> signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
> #1 0x00007f426c2a9d2f in __pthread_kill_internal (signo=6,
> threadid=<optimized
> out>) at ./nptl/pthread_kill.c:78
> #2 0x00007f426c25aef2 in __GI_raise (sig=sig@entry=6) at
> ../sysdeps/posix/raise.c:26
> #3 0x00007f426c245472 in __GI_abort () at ./stdlib/abort.c:79
> #4 0x00007f426c29e2d0 in __libc_message (action=action@entry=do_abort,
> fmt=fmt@entry=0x7f426c3b8459 "%s\n") at ../sysdeps/posix/libc_fatal.c:155
> #5 0x00007f426c2b364a in malloc_printerr (str=str@entry=0x7f426c3b60b1
> "free(): invalid pointer") at ./malloc/malloc.c:5660
> #6 0x00007f426c2b53d4 in _int_free (av=<optimized out>, p=<optimized out>,
> have_lock=have_lock@entry=0) at ./malloc/malloc.c:4435
> #7 0x00007f426c2b7d2f in __GI___libc_free (mem=<optimized out>) at
> ./malloc/malloc.c:3385
> #8 0x00005617abf86e1a in do_search_file (needles=std::vector of length 1,
> capacity 1 = {...}, filename="plocate.db") at ../plocate.cpp:491
> #9 0x00005617abf804b8 in main (argc=<optimized out>, argv=<optimized out>) at
> ../plocate.cpp:995
The stack trace seems somewhat misleading, but I wonder perhaps if this is
https://git.sesse.net/?p=plocate;a=commitdiff;h=7f39444852308224240ebfb75e0bf8f39403afa0
Could you check if downgrading liburing helps? (If so, this shouldn't affect
bookworm as far as I understand)
/* Steinar */
--
Homepage: https://www.sesse.net/
