From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] COG crashes on Pi4 (wpe_webkit)
Date: Sat, 23 May 2020 22:29:48 +0200 [thread overview]
Message-ID: <20200523222948.009d9706@gmx.net> (raw)
In-Reply-To: <1590157038870-0.post@n4.nabble.com>
Hello Daniel,
On Fri, 22 May 2020 09:17:18 -0500 (CDT), usul27 <daniel@hifiberry.com> wrote:
> Ok, finally got a build with debug symbols:
>
> Thread 1 "cog" received signal SIGSEGV, Segmentation fault.
> 0x00000000 in ?? ()
> (gdb) backtrace
> #0 0x00000000 in ?? ()
> #1 0xb1799f84 in ffi_call_SYSV () from /lib/libffi.so.7
> #2 0xb17993fc in ffi_call_int () from /lib/libffi.so.7
> #3 0xb1799b1c in ffi_call () from /lib/libffi.so.7
> #4 0xb149b28c in wl_closure_invoke (closure=closure at entry=0xadb03a00,
> flags=flags at entry=2, target=<optimized out>, opcode=3025639260,
> data=<optimized out>, data at entry=0x74c60) at src/connection.c:1014
> #5 0xb1497db0 in wl_client_connection_data (fd=<optimized out>,
> mask=<optimized out>, data=0x74c60) at src/wayland-server.c:429
> #6 0xb1499608 in wl_event_loop_dispatch (loop=0x5bfc8, timeout=<optimized
> out>) at src/event-loop.c:640
> #7 0xb0c59400 in WS::ServerSource::{lambda(_GSource*, int (*)(void*),
> void*)#3}::_FUN(_GSource*, int (*)(void*), void*) () from
> /lib/libWPEBackend-fdo-1.0.so.1
> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
>
> Somebody has any idea?
Did some test on RPi4 with the following defconfig:
BR2_arm=y
BR2_cortex_a72=y
BR2_ARM_FPU_NEON_VFPV4=y
BR2_ENABLE_DEBUG=y
BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_19=y
BR2_BINUTILS_VERSION_2_31_X=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_PACKAGE_HOST_GDB=y
BR2_GDB_VERSION_8_3=y
BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y
BR2_SYSTEM_DHCP="eth0"
BR2_GENERATE_LOCALE="en_US"
BR2_ROOTFS_POST_BUILD_SCRIPT="board/raspberrypi4/post-build.sh"
BR2_ROOTFS_POST_IMAGE_SCRIPT="board/raspberrypi4/post-image.sh"
BR2_ROOTFS_POST_SCRIPT_ARGS="--add-pi3-miniuart-bt-overlay"
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,raspberrypi,linux,4f2a4cc501c428c940549f39d5562e60404ac4f7)/linux-4f2a4cc501c428c940549f39d5562e60404ac4f7.tar.gz"
BR2_LINUX_KERNEL_DEFCONFIG="bcm2711"
BR2_LINUX_KERNEL_DTS_SUPPORT=y
BR2_LINUX_KERNEL_INTREE_DTS_NAME="bcm2711-rpi-4-b"
BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
BR2_PACKAGE_STRACE=y
BR2_PACKAGE_DEJAVU=y
BR2_PACKAGE_COG=y
BR2_PACKAGE_MESA3D=y
BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_KMSRO=y
BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_V3D=y
BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_VC4=y
BR2_PACKAGE_MESA3D_OPENGL_ES=y
BR2_PACKAGE_WESTON=y
BR2_PACKAGE_WESTON_DRM=y
BR2_PACKAGE_WESTON_DEMO_CLIENTS=y
BR2_PACKAGE_RPI_FIRMWARE=y
BR2_PACKAGE_RPI_FIRMWARE_VARIANT_PI4=y
BR2_PACKAGE_WPEWEBKIT=y
BR2_PACKAGE_OPENSSH=y
BR2_TARGET_ROOTFS_EXT2=y
BR2_TARGET_ROOTFS_EXT2_4=y
BR2_TARGET_ROOTFS_EXT2_LABEL=""
BR2_TARGET_ROOTFS_EXT2_SIZE="256M"
# BR2_TARGET_ROOTFS_TAR is not set
BR2_PACKAGE_HOST_DOSFSTOOLS=y
BR2_PACKAGE_HOST_GENIMAGE=y
BR2_PACKAGE_HOST_MTOOLS=y
Running:
$ export XDG_RUNTIME_DIR=/tmp
$ weston --tty 1 &
$ cog --platform=fdo
leads to the 'Segmentation fault' as you described...
Running:
$ export XDG_RUNTIME_DIR=/tmp
$ weston --tty 1 --backend=drm-backend.so &
$ cog --platform=fdo
works...
Regards,
Peter
>
>
>
>
> --
> Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2020-05-23 20:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 13:16 [Buildroot] COG crashes on Pi4 (wpe_webkit) usul27
2020-05-19 17:44 ` Peter Seiderer
2020-05-20 7:07 ` usul27
2020-05-22 14:17 ` usul27
2020-05-23 20:29 ` Peter Seiderer [this message]
2020-05-24 8:59 ` Daniel HiFiBerry
2020-05-24 9:42 ` Peter Seiderer
2020-05-24 9:43 ` Daniel HiFiBerry
2020-05-24 12:43 ` Peter Seiderer
2020-05-25 7:18 ` Daniel HiFiBerry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200523222948.009d9706@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox