Btw, Record in Sugar works with the same symptoms as Cheese in Gnome (that is, you can take pictures but you don't get a live feed).
Hth, Raúl On Tue, 2009-12-22 at 21:42 -0300, Raul Gutierrez Segales wrote: > Hey guys, > > Is it cheating to change the screen depth? I change it to 24 bpp and now > cheese and totem work. Changes to /etc/X11/xorg.conf: > > (in the Screen Section) > > DefaultDepth 24 > > (in the Display SubSection) > > Depth 24 > > Cheese doesn't show live video from the camera but I am able to take > pictures. And totem reproduces video (no sound, but hey! that it is > another thread/ticket). > > Anything wrong with using X with 24bpp? > > I can feel F11 on the XO-1 near.... :) > > > > On Mon, 2009-12-21 at 23:21 +0000, Tomeu Vizoso wrote: > > Hmm, it's a bit hard to read with so many details, can you run it > > again without -v --leak-check=full --show-reachable=yes ? Those are > > useful when looking for memory leaks. > > > > I would expect that valgrind would complain when the uninitialized > > values get read. > > > > Thanks, > > > > Tomeu > > > > On Mon, Dec 21, 2009 at 20:13, crodas <cro...@paraguayeduca.org> wrote: > > > Hi there, > > > On Sat, 19 Dec 2009 12:06:41 +0000, Tomeu Vizoso <to...@sugarlabs.org> > > > wrote: > > >> On Sat, Dec 19, 2009 at 07:00, John Gilmore <g...@toad.com> wrote: > > >>>> #10 0xb67fae59 in gst_xvimagesink_xvimage_put (xvimagesink=0x8364160) > > >>>> at xvimagesink.c:864 > > >>>> src = {x = 134867456, y = 140758336, w = -1259457208, h = 1} > > >>>> dst = {x = 137730309, y = 3, w = 0, h = 137691184} > > >>>> result = {x = 0, y = 0, w = 322, h = 241} > > >>>> draw_border = 322 > > >>>> __PRETTY_FUNCTION__ = "gst_xvimagesink_xvimage_put" > > >>>> > > >>>> The src.w value is in the same range as the Xlib function addresses; > > >>>> -1259457208 is 0x4B11CAB8 and as can be seen from the call frame #9 > > >>>> the XSync function is at 0x4b0eccf7. The other values seem > > >>>> irrational. This may be evidence that the stack has been corrupted > > >>>> somewhere else, or the values not initialised. > > >>> > > >>> Just to rule out going too far down a blind alley... > > >>> > > >>> Try adding a printf of these values to the code there, rather than or > > >>> in addition to using GDB. GDB may not be 100% reliable when accessing > > >>> variables from optimized code. (I used to maintain GDB, and I worked > > >>> very hard to make it never lie to you, but that precept hasn't always > > >>> been followed in the intervening decade, and optimizations have also > > >>> gotten a lot more complicated.) > > >>> > > >>> Or try compiling that code without -O and see if that changes either > > >>> its behavior, or what the debugger reports. > > >> > > >> At this point is when I would run totem in valgrind, I can help > > >> interpreting the output if it's not clear. > > >> > > >> # yum install valgrind > > >> $ valgrind totem > > > I hope it helps, > > > > > > http://oficina.paraguayeduca.org/~crodas/valgrind-debug.txt > > > > > > cheers, > > > > > >> > > >> Regards, > > >> > > >> Tomeu > > > > > > > > > > > _______________________________________________ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel