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' (tosiara)
2. Re: motion crashing or stops working (tosiara)
----------------------------------------------------------------------
Message: 1
Date: Tue, 9 Feb 2021 13:27:15 +0200
From: tosiara <tosi...@gmail.com>
To: Motion discussion list <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:
<cachtdwqxru4nhwtrjqzj0bsfhlatfwwv-zg6kvg3duudqlk...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
gdb clearly says "Program received signal SIGILL, Illegal instruction"
The code has not been compiled for this target architecture. Di dyou
compile yourslef or used some binary releease? Which?
On Sat, Feb 6, 2021 at 7:20 PM Damo Gets <damo.g...@gmail.com> wrote:
>
> 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
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
------------------------------
Message: 2
Date: Tue, 9 Feb 2021 13:29:08 +0200
From: tosiara <tosi...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] motion crashing or stops working
Message-ID:
<CACHTdwS+tz=ktJh_EyBg9w8UMwQpkHMuBiUrpZVamNUte3=k...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
How do you reproduce the crash? Is it random?
On Sat, Feb 6, 2021 at 6:46 PM S Andreason <sandrea...@gmail.com> wrote:
>
> Hi,
> I sent a gdb backtrace on Dec.25 but never heard any reply, so am
> assuming it got lost. Here is a resend. I have also had it crash
> yesterday right after startup, without changing the mask file etc. Just
> a few screenshots and then disappeared.
> Please reply with ideas for further testing or config file changes.
> Thank you
>
>
> S Andreason wrote:
> > 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
>
>
>
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
------------------------------
------------------------------
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 20
********************************************
