rust-lang / rust-lang/rustlings
"c:check all" causes clippy3 crash
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 64.2k
- Forks
- 11.3k
- Avg merge
- 5h 24m
- Merged PRs (30d)
- 2
Description
Hello,
when I select "c:check all" from the Rustlings menu, I get notified of a crash in the clippy3 executable. I haven't worked on clippy3 yet, and perhaps the crash is due to a deliberate error in the file. Nevertheless the fact that I get a crash report from my OS in this case seems undesirable as it cannot be inferred if this is intended behaviour.
Or am I missing something?
Anyway, here's the stack trace:
#0 0x00007f46990a8fbb pthread_kill (libc.so.6 + 0xa8fbb)
#1 0x00007f46990470a6 raise (libc.so.6 + 0x470a6)
#2 0x00007f46990292db abort (libc.so.6 + 0x292db)
#3 0x0000564472716c1a _RNvNtNtNtCs6ZjlLoI6YmX_3std3sys3pal4unix14abort_internal (clippy3 + 0x3dc1a)
#4 0x00005644727158d9 _RNvNtCs6ZjlLoI6YmX_3std7process5abort (clippy3 + 0x3c8d9)
#5 0x00005644727056da _RNvCs6rREvFdRhLb_7___rustc12___rust_abort (clippy3 + 0x2c6da)
#6 0x00005644726efafa _RNvCs6rREvFdRhLb_7___rustc18___rust_start_panic (clippy3 + 0x16afa)
#7 0x000056447270562e _RNvCs6rREvFdRhLb_7___rustc10rust_panic (clippy3 + 0x2c62e)
#8 0x0000564472715b95 _RNvNtCs6ZjlLoI6YmX_3std9panicking15panic_with_hook (clippy3 + 0x3cb95)
#9 0x0000564472705064 _RNCNvNtCs6ZjlLoI6YmX_3std9panicking13panic_handler0B5_ (clippy3 + 0x2c064)
#10 0x00005644726fa629 _RINvNtNtCs6ZjlLoI6YmX_3std3sys9backtrace26___rust_end_short_backtraceNCNvNtB6_9panicking13panic_handler0zEB6_ (clippy3 + 0x21629)
#11 0x00005644727057bd _RNvCs6rREvFdRhLb_7___rustc17rust_begin_unwind (clippy3 + 0x2c7bd)
#12 0x000056447272a50c _RNvNtCsc36rpYXAlPq_4core9panicking9panic_fmt (clippy3 + 0x5150c)
#13 0x000056447272a4d2 _RNvNtCsc36rpYXAlPq_4core9panicking5panic (clippy3 + 0x514d2)
#14 0x000056447272a229 _RNvNtCsc36rpYXAlPq_4core6option13unwrap_failed (clippy3 + 0x51229)
#15 0x00005644726ef65a _RNvCsk5GCxd0OoC6_7clippy34main (clippy3 + 0x1665a)
#16 0x00005644726ef45b _RNvYFEuINtNtNtCsc36rpYXAlPq_4core3ops8function6FnOnceuE9call_onceCsk5GCxd0OoC6_7clippy3 (clippy3 + 0x1645b)
#17 0x00005644726eeb8e _RINvNtNtCs6ZjlLoI6YmX_3std3sys9backtrace28___rust_begin_short_backtraceFEuuECsk5GCxd0OoC6_7clippy3 (clippy3 + 0x15b8e)
#18 0x00005644726ef581 _RNCINvNtCs6ZjlLoI6YmX_3std2rt10lang_startuE0Csk5GCxd0OoC6_7clippy3 (clippy3 + 0x16581)
#19 0x00005644727150c7 _RNvNtCs6ZjlLoI6YmX_3std2rt19lang_start_internal (clippy3 + 0x3c0c7)
#20 0x00005644726ef567 _RINvNtCs6ZjlLoI6YmX_3std2rt10lang_startuECsk5GCxd0OoC6_7clippy3 (clippy3 + 0x16567)
#21 0x00005644726ef9fe main (clippy3 + 0x169fe)
#22 0x00007f469902b5ac n/a (libc.so.6 + 0x2b5ac)
#23 0x00007f469902b6ca __libc_start_main (libc.so.6 + 0x2b6ca)
#24 0x00005644726ee8e5 _start (clippy3 + 0x158e5)
ELF object binary architecture: AMD x86-64
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the crash by selecting "c:check all" from the Rustlings menu, then inspect the clippy3 exercise and its execution path. The stack trace points to an unwrap failure in clippy3's main function. Done means this action no longer produces an operating-system crash report and its behavior is handled clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100