BUG: Motion 3.2.3 crashes with Seg Fault at first detection
Motion compiled from sources 3.2.3 along with ffmpeg-devel-0.4.9-0.lvn.0.18.20050801.3 & ffmpeg-0.4.9-0.lvn.0.18.20050801.3 causes it to Seg Fault when motion is first detected.
I am using an X10 USB camera with the spca5xx driver.
Another setup using this camera & USB capture device along with compiled motion 3.1.19 using rpms ffmpeg-devel-0.4.8-3.1.fc2.dag; ffmpeg-0.4.8-3.1.fc2.fr on a FC2 2.6.5-1.358 works fine!
I am trying to run motion on an Linux version 2.6.12-1.1372_FC3 (bhcompile@tweetyPLEASENOSPAM.build.redhat.com
) (gcc version 3.4.3 20050227 (Red Hat 3.4.3-22)) #1 Fri Jul 15 00:59:10 EDT 2005
I compiled motion from source but it crashes as soon as it detects motion. Could you help please? Here is a backtrace:
[motion-3.2.3]# gdb /usr/local/bin/motion
GNU gdb Red Hat Linux (6.1post-1.20040607.43rh)
Copyright 2004 Free Software Foundation, Inc.
This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/tls/libthread_db.so.1".
Starting program: /usr/local/bin/motion
Reading symbols from shared object read from target memory...done.
Loaded system supplied DSO at 0xf78000
[Thread debugging using libthread_db enabled]
[New Thread -1208936768 (LWP 14004)]
 Processing thread 0 - config file /usr/local/etc/motion.conf
 Thread is from /usr/local/etc/motion.conf
[New Thread -1208939600 (LWP 14007)]
 Thread started
[New Thread -1219429456 (LWP 14008)]
 motion-httpd/3.2.3 running, accepting connections
 motion-httpd: waiting for data on port TCP 8080
 Started stream webcam server in port 8081
 File of type 8 saved to: /tmp/motion/backup/01-20051202014757.avi
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208939600 (LWP 14007)]
ffmpeg_put_frame (cnt=0x9538f80, ffmpeg=0x9537fc0, pic=0x9554730) at ffmpeg.c:522
522 pkt.pts = AVSTREAM_CODEC_PTR(ffmpeg->video_st)->coded_frame->pts;
(gdb) bt full
#0 ffmpeg_put_frame (cnt=0x9538f80, ffmpeg=0x9537fc0, pic=0x9554730) at ffmpeg.c:522
out_size = 745
ret = Variable "ret" is not available.
I have the following RPMs installed:
My motion.conf is attached to this report...
| Motion version:
| ffmpeg version:
| Shared libraries:
| Server OS:
- 02 Dec 2005
Did you install Motion from RPM.
Someone just reported that my download link pointed to the old version which indeed fails with the newer ffmpeg versions.
Link is correct now. If you compiled from source Motion should have built itself correctly.
Note. You do not need to put %BR% after each line. To show errors/logs etc just put the text inside <VERBATIM> and </VERBATIM> tages. Like I just did.
- 02 Dec 2005
Assume the wrong link at Download was the issue.
- 18 Dec 2005