Quick update: I've tried all these docker base images:
busybox:1.3{4,5,6}-{musl,uclibc,glibc} and I can only reproduce the failure in
1.36 - but it does fail with all three stdlib variants.
These docker images contain the core dump:
ghcr.io/backplane/avxtest:1.36-glibc-1677653916
ghcr.io/backplane/avxtest:1.36-uclibc-1677653904
<http://ghcr.io/backplane/avxtest:1.36-uclibc-1677653904>
ghcr.io/backplane/avxtest:1.36-musl-1677653897
You can look at these images without downloading them by using
https://explore.ggcr.dev/
Here are some direct links to browse the filesystem of in those images (and see
the cores):
https://explore.ggcr.dev/layers/ghcr.io/backplane/avxtest:1.36-glibc-1677653916@sha256:16b6212308944e247fd275ed73cf57768fbd3f6442fd92e790755fd72bf6ca71/
https://explore.ggcr.dev/layers/ghcr.io/backplane/avxtest:1.36-uclibc-1677653904@sha256:964053d7a517abb5214286fbf43849a795344ef2c136431ff1cfeafce5d76af6/
https://explore.ggcr.dev/layers/ghcr.io/backplane/avxtest:1.36-musl-1677653897@sha256:53be164ff4070b4db5493c6d223dd9cfc872d6bfc712c8b6b4d4dd3fcc645b9f/
My dockerfile is now very simple:
https://raw.githubusercontent.com/backplane/avxtest/main/Dockerfile
The workflow is here:
https://raw.githubusercontent.com/backplane/avxtest/main/.github/workflows/docker-publish.yml
Peter - I have been able to get gdb going on the core file but I'm not
experienced enough to be able to get much out of it when the binary is stripped
and optimised like this. I can disassemble address ranges in the core dump with
like "disassemble $fp-32, $fp+32" but I'm out of my depth. I'll look into
getting a shell on the GitHub Actions runner to debug it in real time.
> On 1 Mar 2023, at 7:34 AM, Peter Faasse <p.faa...@chello.nl> wrote:
>
> On dinsdag 28 februari 2023 23:17:19 CET ben.busy...@backplane.be wrote:
>> Hi,
>>
>> I'm having an intermittent issue with "BusyBox v1.36.0 (2023-01-03 22:49:12
>> UTC)" (the one from the Docker image busybox:musl) when running on amd64
>> GitHub actions runner VMs (azure).
>>
>> When I use sha256sum it is getting terminated with SIGILL, Illegal
>> instruction. The issue is hard to reproduce but I have a GitHub actions
>> CI/CD job that I can re-run repeatedly (no changes to code, environment,
>> data input, etc) that will occasionally have the issue. I managed to
>> capture a core dump.
>
> << snipped >>>
>> Any idea what's going on?
>
> Bad RAM? H/W (bus) problems?? This smells like hardware problems more than
> software :-/
>
> As to analyzing: Is running 'it' with the debugger feasible? Or loading the
> core dump into the debugger... Then compare 'ok' with 'fail' (from core-dump)
> to see what / where the problem lurks.
>
>> Thanks,
>> Ben
>
> Kind regards,
> Peter
>
> --
> The PGP PUBLIC KEY BLOCK below is my response to the traditional useless
> disclaimer found at the end of e-mails.
>
> This public PGP key is one member of a pair of public/private PGP keys
> that I have generated on my computer in less than a minute..
>
> You could use this public PGP key to:
>
> - Verify that this message is the unchanged message as sent by me,
> using the digital signature of this e-mail and this public PGP key.
> My mail-program signs all sent e-mail using my private PGP key.
> - Encrypt any e-mail you send to me, so only I can decrypt it using my
> private PGP key. I prefer to receive so-encrypted e-mail; My mail program
> decrypts all e-mails that are encrypted using this public PGP key.
>
> You could do the same. If you have a public and private PGP key pair,
> please provide your public PGP key to me.
>
> - I will use it to check the integrity of e-mail received from you, if you
> sign your e-mail.
> - If you so prefer, I will use it to encrypt all my e-mail to you, so only you
> can decrypt and read e-mail sent from me to you.
>
> All e-mail programs support automatically and transparently performing
> the above-mentioned steps that implement these privacy-enhancing
> measures, using freely-available tools.
>
> -----BEGIN PGP PUBLIC KEY BLOCK-----
>
> mQENBFFgk6cBCACVLaCELJZMnbjcjmvnyI74YGVTs7iPchuFNIFLW7Y4UBxB8JFc
> sZOUT5LrJV9+ebCX2eVh1+n79Z4QuzRDTlsznToON6yA31jK3R057tJcmc4CVSjI
> 1+SpDRhDMsEPYId7IgGacezKuVPbbDqEVZZXkUj/7kyyaaWR1eNN4exJQ6DcVkfd
> 9c1Kv9blom3DbWeqkkTWqWxRT5bnFAVB8xLrFE2sA0D/cFejX/WxMmZXJEPhIZT9
> eKqND7LMGQF/XwIzO11IsyB/7aFD2dfemgNiWf9rD7++knRjrCYPADB1cK6XbD8r
> rm6LYhK3PnkHfb8BG0mU78dB4LyOqE8UdFtHABEBAAG0LlBldGVyIEZhYXNzZSAo
> ZS1tYWlsIGtleSkgPHAuZmFhc2UxQGNoZWxsby5ubD6JATgEEwECACIFAlFgk6cC
> Gw8GCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEGxmOUkWLm1ykfEH/A9sCA20
> BcaMxXsdkKH78Y2yIwVkPCSpHHsnrYQUBOPqUF2i0iimEgol0NwN4BD4OOsuUmmG
> y2re9HzmIL+AwtqMg8JPw3Pw1d1+MzRldKm4f7cZMhi0p78xvi6bCaFNBAqJHD97
> q70k3t46BlFQk2alMQKpLcB2xaWQuxn8rhr8HJMlpNbJ4Ifh9jNn/SeYvXyxbSrA
> qzUJ4r4cWLGJ6tdKzmiem3CV8hOU5CdtAfi/RhtwGTU27glNyVmkdpE1o9QYR1q3
> P7TRavdtdCNX0sl7OlN5Go2O9jWt2igsiiyjS2KlytCVONRilH1FAMaXtcPs/KU9
> tvOxHkbVz6bfXOg=
> =oiSn
> -----END PGP PUBLIC KEY BLOCK-----
> _______________________________________________
> busybox mailing list
> busybox@busybox.net
> http://lists.busybox.net/mailman/listinfo/busybox
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
