Re: spcagui - segmentation fault Kubuntu 7.10, Suse 10.3
"Denver Gingerich" <[email protected]>
| Newsgroups | gmane.linux.drivers.spca50x.devel |
|---|---|
| Message-ID | <[email protected]> |
On Jan 28, 2008 1:23 PM, jansuz <[email protected]> wrote: > I tried to use spcagui to check if I can change parameters to get better > picture. > The program was compiled without any problems on Kubuntu 7.10 amd64 and > 32 bit Suse 10.3. But when I try to run it it crashes with the > segmentation fault on both systems. > Can anybody suggest any reason and the way to solve the problem? > > Below is the output from the spcagui. > > Jansuz > > $ ./spcagui > SpcaGui version: 0.3.5 date: 18 September 2005 > video device /dev/video0 > Camera found: Labtec Webcam Pro > VIDIOCGPICT brightnes=32768 hue=0 color=0 contrast=32768 > whiteness=0depth=24 palette=4 > Bridge found: ZC301-2 > Unable to find a StreamId !! > StreamId: 6 Unknow Camera > try palette 15 depth 12 > Available palette 15 > try palette 3 depth 16 > Available palette 3 > try palette 4 depth 24 > Available palette 4 > try palette 5 depth 32 > Available palette 5 > probe size in > Available Resolutions width 640 heigth 480 > Available Resolutions width 384 heigth 288 > Available Resolutions width 352 heigth 288 > Available Resolutions width 320 heigth 240 > Available Resolutions width 192 heigth 144 > Available Resolutions width 176 heigth 144 > grabbing method default MMAP asked > VIDIOCGMBUF size 2457632 frames 2 offets[0]=0 offsets[1]=1228816 > VIDIOCGPICT brightnes=32768 hue=0 color=0 contrast=32768 > whiteness=0depth=12 palette=15 > VIDIOCGPICT brightnes=32768 hue=0 color=0 contrast=32768 > whiteness=0depth=12 palette=15 > VIDIOCGPICT brightnes=32768 hue=0 color=0 contrast=32768 > whiteness=0depth=12 palette=15 > VIDIOCSPICT brightnes=32768 hue=0 color=0 contrast=32768 > whiteness=0depth=12 palette=15 > Segmentation fault (core dumped) Can you send a backtrace? This can be done by doing the following: $ gdb ./spcagui ... (gdb) run ... [SIGSEGV] (gdb) backtrace [send us the stuff you get here] This will show us the functions that were being called at the time the segfault occurred. I'm not sure if it's compiled with debugging symbols by default; if it is, then we may need you to re-send the backtrace after compiling with -g, but just send us the backtrace for now. Denver ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/