https://bugzilla.suse.com/show_bug.cgi?id=1213353 https://bugzilla.suse.com/show_bug.cgi?id=1213353#c15 --- Comment #15 from Dr. Werner Fink <werner@suse.com> --- (In reply to Christian Boltz from comment #14)
(In reply to Dr. Werner Fink from comment #9)
OK ... that is what we already know ... the real reason/cause would be a win. Error in bash/libreadline ... or in (g)libc ... or overheated system
Given the hot weather in the last days, I wouldn't rule out overheated system. However, this was the only strange issue I noticed during these hot days.
If the autocomplete of the bash/libreadline is the reason the dump is not that useful as the abort() of the glibc had detected an error which had already happen (IMHO) and in the dump the backtrace (even with full option) shows an other action which belongs to the executable systemct below /home/cb/bin/ ... note the missing `l' to get a complete systemctl located in /usr/bin/ In bash mailing list Grisha Levit had found via AddressSanitizer of the gcc some bug e.g. in parse.y but this was for current devel version not bash 5.2 ... nevertheless the e.g. the use-after-free of ttok is also in 5.2 AFAICS -- You are receiving this mail because: You are on the CC list for the bug.