Segmentationfault on netcam

Question

For some reason, I suddenly get a Segmentation fault when I start motion. it seems that it is when it starts the netcam module. If I remove all the netcam threads and just leave the usb cam thread it runs smoothly. What packages does the netcam module depend upon? Maybe some of them needs to be rebuilt. I have recently compiled new versions of many packages, so there may be something there..

[0] Processing thread 0 - config file /etc/motion.conf
[0] Processing config file /etc/motion/camera_1.conf
[0] Processing config file /etc/motion/camera_2.conf
[0] Processing config file /etc/motion/camera_3.conf
[0] Processing config file /etc/motion/camera_4.conf
[0] Processing config file /etc/motion/camera_5.conf
[0] Thread 1 is from /etc/motion/camera_1.conf
[0] Thread 2 is from /etc/motion/camera_2.conf
[0] Thread 3 is from /etc/motion/camera_3.conf
[0] Thread 4 is from /etc/motion/camera_4.conf
[0] Thread 5 is from /etc/motion/camera_5.conf
[1] Thread started
[2] Thread started
[3] Thread started
[4] Thread started
[5] Thread started
[0] motion-httpd/3.2.7 running, accepting connections
[0] motion-httpd: waiting for data on port TCP 8080
[3] Started stream webcam server in port 7773
Segmentation fault

Environment

Motion version:	3.2.7
ffmpeg version:	0.4.9_p20060530
Libraries:	ffmpeg, mysql
Server OS:	2.6.12-gentoo-r10

-- GunnarSkjold - 05 Nov 2006

Actually I just found out that the usb cam thread also dies if I try to access the live stream on the webcam server.

-- GunnarSkjold - 05 Nov 2006

Installed 3.2.6 instead and it works

Somehow 3.2.7 does not fit my system. Please let me know if there is anything I can do to help

-- GunnarSkjold - 05 Nov 2006

Answer

It concerns me if 3.2.6 works and 3.2.7 does not.

Can you try and run it again and tell us what you get in your syslog?

Also can you post your config files? You can simply attach them. Remember to delete passwords.

-- KennethLavrsen - 05 Nov 2006

Sorry for taking so long. Ill try to do it next week.

-- GunnarSkjold - 22 Nov 2006

Sorry about all this. Now it works fine offcourse.. Maybe I have upgraded some important dependency since last time. Im not sure.