embedded debugging

[SummoningDark]

I am having a problem doing remote debugging on an ARM linux system after changing the root filesystem. My setup is as follows:

embedded processor Xilinx zynq xz7020 (Avnet Microzed)
Qt version 5.15.2
Linux kernel and SDK were built using the Xilinx petalinux 2021.2 tools
system runs off an SD card wit separate boot and rootfs partitions.

When I run the petalinux kernel and petalinux rootfs on the target everything works great. However the petalinux root filesystem is super annoying since I have to build everything from scratch if I want to add packages, so I downloaded an ubuntu root filesystem and set that up. The ubuntu rootfs is great, and executables built in QtCreator with the xilinx sdk (on a host x86_64 machine) run without issue. However I can't use the remote debugging on the ubuntu root filesystem. I can deploy and run fine, so the connection isn't the issue. I can run the target executable in gdbserver manually, and connect manually from the host. However when I try to debug from the Qt creator IDE I get the message:
"The inferior stopped because it received a signal from the operating system SIGSEGV"
All of the deployment steps finish without issue, then I get the message. This happens before the target executable is run (basically I can't put a breakpoint anywhere that catches it, and the program runs fine when not debugging)

Are there logs anywhere that would let me see what exactly is failing? or some script where I can see the exact steps QtCreator is doing to run and connect to the gdb server?

Thanks,
Jenn

[SummoningDark]

@jbarrena
hi Julen,
I fixed the problem by changing the sysroot option in my kit to point at my ubuntu rootfs instead of the petalinux one. Thanks for your help.

Jenn

[jbarrena]

Hi Jenn.

It seems that you are not fetching your device environment in your project. It usually happens when you have a Linux Embedded device running on your platform. Check out whether you have fetched your device environment inside your kit's run settings:

Hope this helps. Kind regards.
Julen.

[SummoningDark]

@jbarrena
hi Julen,
I fixed the problem by changing the sysroot option in my kit to point at my ubuntu rootfs instead of the petalinux one. Thanks for your help.

Jenn