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 crashing or stops working (S Andreason)
----------------------------------------------------------------------
Message: 1
Date: Fri, 25 Dec 2020 09:02:53 -0800
From: S Andreason <sandrea...@gmail.com>
To: Motion-user <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] motion crashing or stops working
Message-ID: <4dec5771-d3bf-1a00-343a-b4a63b6e5...@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi,
I reported I've been having motion crash (sometimes), without error
messages, usually when performing a restart for a single camera after
changing the mask_file setting. (I do this a lot.)
I now have something substantial to help figure this out, after running
motion directly (not as a service), I saw a Segmentation Fault message,
this time at startup instead of the restart. So I started gdb, and here
is the backtrace.
$ sudo gdb motion
GNU gdb (Raspbian 8.2.1-2) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
[clip]
This GDB was configured as "arm-linux-gnueabihf".
[clip]
Reading symbols from motion...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/motion
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/arm-linux-gnueabihf/libthread_db.so.1".
[0:motion] [NTC] [ALL] conf_load: Processing thread 0 - config file
/etc/motion/motion.conf
[0:motion] [NTC] [ALL] config_camera: Processing camera config file
/etc/motion/camera206.conf
[0:motion] [NTC] [ALL] config_camera: Processing camera config file
/etc/motion/camera204.conf
[0:motion] [NTC] [ALL] motion_startup: Logging to file
(/var/log/motion/motion.log)
[New Thread 0xadca0a90 (LWP 3992)]
[New Thread 0xad2fea90 (LWP 3993)]
[New Thread 0xac484a90 (LWP 3994)]
[New Thread 0xabc83a90 (LWP 3995)]
[New Thread 0xaac3aa90 (LWP 3999)]
[New Thread 0xa9c3aa90 (LWP 4000)]
Thread 7 "nc4:204_Alptop_" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa9c3aa90 (LWP 4000)]
0xb5919790 in ?? () from
/usr/lib/arm-linux-gnueabihf/neon/vfp/libavcodec.so.58
(gdb) bt
#0? 0xb5919790 in ?? () from
/usr/lib/arm-linux-gnueabihf/neon/vfp/libavcodec.so.58
#1? 0xb590ef7c in ?? () from
/usr/lib/arm-linux-gnueabihf/neon/vfp/libavcodec.so.58
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Stewart
------------------------------
------------------------------
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 174, Issue 8
*******************************************
