From: usul27 <daniel@hifiberry.com>
To: buildroot@busybox.net
Subject: [Buildroot] COG crashes on Pi4 (wpe_webkit)
Date: Fri, 22 May 2020 09:17:18 -0500 (CDT) [thread overview]
Message-ID: <1590157038870-0.post@n4.nabble.com> (raw)
In-Reply-To: <1589958433571-0.post@n4.nabble.com>
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?
--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
next prev parent reply other threads:[~2020-05-22 14:17 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 [this message]
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=1590157038870-0.post@n4.nabble.com \
--to=daniel@hifiberry.com \
--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