seg fault on 64 bit ARM

[Tim Müller]

On Thu, 2017-01-19 at 12:38 -0500, Rand Graham wrote:

Hi,

> Caught SIGSEGV
> Spinning.  Please run 'gdb gst-launch-1.0 22424' to continue
> debugging, Ctrl-C to quit, or Ctrl-\ to dump core.
>  ...
> 
> --gdb backtrace:
> (gdb) backtrace
> #0  0x0000007f987b20e0 in __GI___poll (fds=0x424020, nfds=2,
> timeout=<optimized out>) at
> ../sysdeps/unix/sysv/linux/generic/poll.c:38
> #1  0x0000007f988b23c4 in ?? () from /lib/aarch64-linux-gnu/libglib-
> 2.0.so.0
> #2  0x00000000004ceae0 in ?? ()
> Backtrace stopped: previous frame inner to this frame (corrupt
> stack?)

No, we can't tell what's wrong from that. You'll have to debug it.

It's unlikely to be related to that warning debug message.

Start by getting a stack trace of *all* threads, I don't think the
thread you pasted there is the thread that crashes.

 (gdb) thread apply all bt

Cheers
 -Tim

-- 
Tim Müller, Centricular Ltd - http://www.centricular.com