-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash si_signo=Illegal instruction(4)
when running dart run build_runner build
with dart-musl image on StarFive Visionfive 2 RISC-V board
#56671
Comments
Summary: The user is experiencing a crash with the error "Illegal instruction(4)" when running |
The build command works for me on Debian RISCV64 with the official build. I'm not able to run the musl version on my RV device because of some docker network issue. Can you run this under gdb and disassemble around the bad address?
Or run with the VM's disassembler and search backwords for the address?
|
@rmacnak-google here's the output from
Then
|
For completeness I tried the same sequence on my Ubuntu (and hence glibc) based build image and that also crashes (in this case at
Following a similar process with gdb --args dart pub get --enforce-lockfile
...
(gdb) run
I'd note that the same sequence (and more) runs inside of Docker buildx (hence using QEMU) every time we release binaries, and whilst it hangs far too frequently it doesn't crash in this manner. Given the recent differential fuzzing that targeted both QEMU and the JH7110 SoC in the VisionFive 2 (amongst others) I'm surprised by the differing behaviours I'm seeing here. |
and for further completeness I ran the sequence without Docker (just Ubuntu 24.04.1 on the StarFive VisionFive 2) and no crash. So maybe Docker is the underlying cause?
|
Hm, the instructions seems reasonable. I wonder if this is something like a previous issue seen with Docker with instruction mapping. Can you try running with the background compiler disabled? If this succeeds, it could be something related to instruction synchronization.
|
Good call @rmacnak-google
I recall that previous issue (and especially @mraleph gripes about not being able to reproduce it due to not being allowed Docker Desktop) as my colleague @cconstab hit a similar issue with arm that features later in the thread. The
|
Dart SDK version: 3.5.2 (stable) (Wed Aug 28 10:01:20 2024 +0000) on "linux_riscv64"
Whilst running
dart run build_runner build
on RISC-V (using the dart-musl image):The command sequence that led to that was:
The same sequence (and more) runs just fine on x64.
The text was updated successfully, but these errors were encountered: