Program received signal SIGILL, Illegal instruction.
vgPlain_am_startup (sp_at_startup=3204445696) at
m_aspacemgr/aspacemgr-linux.c:1626
1626 init_nsegment(&seg);
(gdb) x/i $pc
=> 0x58071090 : vmov.i32d16, #0 ; 0x
As a reminder I do not have neon on this machine:
Feature
On 29/06/2022 15:49, Mathieu Malaterre wrote:
Here is what I get on first try:
Program received signal SIGILL, Illegal instruction.
vgPlain_am_startup (sp_at_startup=3204445696) at
m_aspacemgr/aspacemgr-linux.c:1626
1626 init_nsegment(&seg);
(gdb) x/i $pc
=> 0x58071090 : vmov.i32
On Wed, Jun 29, 2022 at 4:27 PM John Reiser wrote:
> -
> (gdb) run args...
> Program received signal SIGILL, Illegal instruction.
> (gdb) x/i $pc ## the faulting instruction
> (gdb) x/12i pc-6*4 ## disassemble the surrounding instructions
> (Gdb) x/12xw $pc-6*4 ## and in 32-bit raw hex
I did not make up those strace logs in my head, all I am trying to do
is Debian bug triaging. Turns out I did a pretty bad job at it:
1. The original Debian bug report seems to be PEBCAK, and I'll close
the bug as wontfix ASAP,
2. I was not paying attention to the gcc version I was using.
Th
On Tue, Jun 28, 2022 at 8:55 PM John Reiser wrote:
>
> >> $ export RPI_MODEL=3
> >> $ export DEBIAN_RELEASE=bullseye
> >> $
> >> wgethttps://raspi.debian.net/daily/raspi_${RPI_MODEL}_${DEBIAN_RELEASE}.img.xz
> >
> > That gives arm64, not armhf (32-bit).
>
> Choosing https://raspi.debian.net/teste
