From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] COG crashes on Pi4 (wpe_webkit)
Date: Tue, 19 May 2020 19:44:00 +0200 [thread overview]
Message-ID: <20200519194400.3edad316@gmx.net> (raw)
In-Reply-To: <1589894180081-0.post@n4.nabble.com>
Hello Daniel,
On Tue, 19 May 2020 08:16:20 -0500 (CDT), usul27 <daniel@hifiberry.com> wrote:
> I'm using the latest release candidate on the Raspberry Pi 3 and 4. While the
> Pi3 version works well, the wpe_webkit browser crashes. I don't have a
> version with debug symbols running, but maybe somebody have seen this
> already and has some hint:
>
> (gdb) backtrace
> #0 0x00000000 in ?? ()
> #1 0xb26382cc in ?? () from /lib/libffi.so.7
> #2 0xb2637c94 in ?? () from /lib/libffi.so.7
> #3 0xb2637f24 in ffi_call () from /lib/libffi.so.7
> #4 0xb2380c30 in ?? () from /lib/libwayland-server.so.0
> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
>
> Weston is using the DRM backend:
> /usr/bin/weston --backend=drm-backend.so --modules=systemd-notify.so
No known failure (at least for me), can you share your config (or defconfig)?
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-19 17:44 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 [this message]
2020-05-20 7:07 ` usul27
2020-05-22 14:17 ` usul27
2020-05-23 20:29 ` Peter Seiderer
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=20200519194400.3edad316@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