RipGrep musl binaries occasionally segfault during very-large searches
1–10 of 216 posts
Re: RipGrep musl binaries occasionally segfault during very-large searches
#2wow, everything is broken lol
Re: RipGrep musl binaries occasionally segfault during very-large searches
#3The analysis of the kernel bug may be a better thing to link to: https://github.com/dfoxfranke/ripgrep-3494-analysis.
Re: RipGrep musl binaries occasionally segfault during very-large searches
#4The analysis of the kernel bug may be a better thing to link to: https://github.com/dfoxfranke/ripgrep-3494-analysis .
soulless unreadable AI slop
Re: RipGrep musl binaries occasionally segfault during very-large searches
#5The analysis of the kernel bug may be a better thing to link to: https://github.com/dfoxfranke/ripgrep-3494-analysis .
soulless unreadable AI slop
I can read it but not sure if worth spending energy on it.
It doesn't make sense for the reader to spend more energy than the writer spent on creating it.
Re: RipGrep musl binaries occasionally segfault during very-large searches
#6Re: RipGrep musl binaries occasionally segfault during very-large searches
#7So, why the bug triggers only with muslc and not other libc ?
Re: RipGrep musl binaries occasionally segfault during very-large searches
#8The analysis of the kernel bug may be a better thing to link to: https://github.com/dfoxfranke/ripgrep-3494-analysis .
soulless unreadable AI slop
Why is it unreadable? I actually find LLM bug reports/breakdowns to be far more detailed and concise that classical human written ones. If you read the linked repo it clearly goes it depth where the bug was found, how to reproduce it (and in depth). Most disclosures that are human written don't do this at all, they barely even tell you _how_ to reproduce the bug. Just look at the "3.3 The self-store tear", the LLM clearly describes exactly what went wrong, so you can verify it by hand.
Re: RipGrep musl binaries occasionally segfault during very-large searches
#9I would normally suspect musl's thread stack size. Is the kernel bug confirmed?
Re: RipGrep musl binaries occasionally segfault during very-large searches
#10Earlier quoted context omitted.
soulless unreadable AI slop
I can read it but not sure if worth spending energy on it. It doesn't make sense for the reader to spend more energy than the writer spent on creating it.
> It doesn't make sense for the reader to spend more energy than the writer spent on creating it.
Great way to summarize cultural "economics"
Couldn't put the words on this pattern but sometimes all I care about is that someone cared about.