Clippy crashes due to SIGABRT (signal: 6, SIGABRT: process abort signal)

Description

Hi, I am not sure how to report this bug, (possibly it is not a bug), but I don't know how to proceed.
I appreciate any suggestion that you can provide me and be able to run clippy, and obtain the root cause of the issue.

Many thanks,
Fernando

> cargo clippy
error: process didn't exit successfully: `/home/fernando/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/clippy-driver /home/fernando/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc -vV` (signal: 6, SIGABRT: process abort signal)
--- stdout
rustc 1.85.1 (4eb161250 2025-03-15)
binary: rustc
commit-hash: 4eb161250e340c8f48f66e2b929ef4a5bed7c181
commit-date: 2025-03-15
host: x86_64-unknown-linux-gnu
release: 1.85.1
LLVM version: 19.1.7

--- stderr
double free or corruption (out)

double free or corruption (out)
[1]    4363 IOT instruction (core dumped)  cargo clippy
exit 134

~/.cargo/bin> ./clippy-driver -V
clippy 0.1.85 (4eb161250e 2025-03-15)
free(): double free detected in tcache 2
[1]    4711 IOT instruction (core dumped)  ./clippy-driver -V
exit 134

~/.cargo/bin> lsb_release -a
No LSB modules are available.
Distributor ID: Neon
Description:    KDE neon 6.3
Release:        24.04
Codename:       noble

> rustup toolchain list
stable-x86_64-unknown-linux-gnu (active, default)
nightly-x86_64-unknown-linux-gnu

Similar closed issues:

• clippy crashes due to SIGABRT #8514

Version

rustc 1.85.1 (4eb161250 2025-03-15)
binary: rustc
commit-hash: 4eb161250e340c8f48f66e2b929ef4a5bed7c181
commit-date: 2025-03-15
host: x86_64-unknown-linux-gnu
release: 1.85.1
LLVM version: 19.1.7

Additional Labels

No response

Start by reproducing cargo clippy and ./clippy-driver -V with Rust 1.85.1 on the reported KDE neon 6.3 environment, then compare the stable and nightly toolchains listed in the report. Trace the double-free or corruption failure and confirm that both commands complete without SIGABRT; the issue names no source file or regression test.