Send Motion-user mailing list submissions to
motion-user@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
motion-user-requ...@lists.sourceforge.net
You can reach the person managing the list at
motion-user-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: motion 4.3.1&4.3.2 both crash after a variable amount of
time on obsd 6.8 armv7 arch with 'bus error' (Damo Gets)
2. Re: motion 4.3.1&4.3.2 both crash after a variable amount of
time on obsd 6.8 armv7 arch with 'bus error' (Damo Gets)
----------------------------------------------------------------------
Message: 1
Date: Sat, 6 Feb 2021 11:14:21 -0600
From: Damo Gets <damo.g...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] motion 4.3.1&4.3.2 both crash after a
variable amount of time on obsd 6.8 armv7 arch with 'bus error'
Message-ID: <20210206111117.30255...@d-resources.hopto.org>
Content-Type: text/plain; charset="us-ascii"
Okay, forgive me if I'm not doing this correctly... I've not done
anything with gdb in forever and I had to look up how to even get the
backtrace.
Here is my gdb session:
-
borgi# gdb -q motion
(gdb) run
Starting program: /usr/local/bin/motion
Error while reading shared library symbols:
Dwarf Error: wrong version in compilation unit header (is 4, should be
2) [in module /usr/libexec/ld.so]
Program received signal SIGILL, Illegal instruction.
0x70da6b80 in _armv8_pmull_probe () at
/usr/src/lib/libcrypto/armv4cpuid.S:91 91
/usr/src/lib/libcrypto/armv4cpuid.S: No such file or directory. in
/usr/src/lib/libcrypto/armv4cpuid.S
Current language: auto; currently asm
(gdb) backtrace
#0 0x70da6b80 in _armv8_pmull_probe () at
/usr/src/lib/libcrypto/armv4cpuid.S:91
#1 0x70dd32dc in OPENSSL_cpuid_setup () at
/usr/src/lib/libcrypto/armcap.c:69
#2 0x7077e21c in ?? () from /usr/libexec/ld.so
(gdb)
-
I've got to admit I think that I did something wrong here, because I
never even got to see the console output that was displayed previously,
leading up to the 'image_ring_resize: Resizing pre_capture buffer to 4
items' message. It actually runs for awhile there before it
crashes, too. With this gdb session none of that is happening, it's
just spitting that out right off the bat.
If I'm doing something wrong here, which I'm thinking I pretty much
must be, can somebody tell me how to go about getting the appropriate
stack trace?
Thank you!
On Sat, 6 Feb 2021 17:30:00 +0200
tosiara <tosi...@gmail.com> wrote:
> Can you run motion from gdb and collect backtrace?
--
-D4m0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
------------------------------
Message: 2
Date: Sat, 6 Feb 2021 11:19:08 -0600
From: Damo Gets <damo.g...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] motion 4.3.1&4.3.2 both crash after a
variable amount of time on obsd 6.8 armv7 arch with 'bus error'
Message-ID: <20210206111908.5402e...@d-resources.hopto.org>
Content-Type: text/plain; charset="us-ascii"
Sorry for the double tag on the mail list here, but I just wanted to
mention that I just realized that it only crashes when it detects
motion, as well...
On Sat, 6 Feb 2021 17:30:00 +0200
tosiara <tosi...@gmail.com> wrote:
> Can you run motion from gdb and collect backtrace?
--
-D4m0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 176, Issue 18
********************************************
