Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 26 Apr 1998 20:16:27 -0400
From:      Randall Hopper <rhh@ct.picker.com>
To:        tomppa@fidata.fi, Amancio Hasty <hasty@rah.star-gate.com>
Cc:        freebsd-multimedia@FreeBSD.ORG
Subject:   Re: problem capturing video with BT848/Haughpage Win/Tv
Message-ID:  <19980426201627.A21132@ct.picker.com>
In-Reply-To: <13626.35483.87697.62123@zeta.fidata.fi>; from Tomi Vainio on Mon, Apr 20, 1998 at 02:36:59AM %2B0300
References:  <199804191831.UAA02048@sos.freebsd.dk> <199804191909.MAA05397@rah.star-gate.com> <13626.35483.87697.62123@zeta.fidata.fi>

next in thread | previous in thread | raw e-mail | index | archive | help

--5vNYLRcllDrimb99
Content-Type: text/plain; charset=us-ascii

Tomi Vainio:
 |Amancio Hasty writes:
 | > Do we have any other PAL users experiencing core dumps when a
 | > full-size fxtv window is moved around?
 | > 
 |I don't even have to move window.  It's enough just to put another
 |window over fxtv and fxtv starts using ximages.  Full size PAL window
 |will give core dump every time.  Maximum size for window is about
 |702x583 and 716x595 is too big.
...
 |tick:~/src/fxtv/work/fxtv-0.46(11)# gdb ./fxtv fxtv.core
...
 |(gdb) bt
 |#0  0x20215562 in ?? ()
 |#1  0xefbfd6cc in ?? ()
 |#2  0xd636 in TVNewFrameHdlr (img=0xefbfd6c8) at tv.c:178

Odd.  I'm going to need a few more tips to help with this one.  

   1) When you get a sec, please run "fxtv -synchronous" and core dump it
      :-) Then dump the stack in gdb.  Hopefully that'll give you a more
      interesting stack.  

      If you don't mind, just mail me the core file.

      It'll be a big help if this was an fxtv compiled for debug.  It's
      easy to build it this way.  Grab:
      http://multiverse.com/~rhh/fxtv/fxtv-0.46.tgz, edit Makefile and swap
      which of the 2 CFLAGS and the 2 LDFLAGS lines is uncommented, and
      then run "gmake".

   2) Please mail your "fxtv -debug startup" and "xdpyinfo" output.
      Might try this in other color depths (e.g. "startx -- -bpp 8" and
      see if you have the same problem).

   3) You can determine if shared vs. non-shared ximages is even involved
      with this problem by applying no-shm-ximages.patch (attached) and
      rebuilding Fxtv 0.46.  I'm going to guess this will not make a diff
      and will still dump core when using non-shared XImages.  

      My best guess is that frame conversion is overrunning the image
      buffer, but I don't know why it would yet.

Randall

--5vNYLRcllDrimb99
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="no-shm-ximages.patch"

--- ORIG/tvscreen.c	Wed Nov  5 01:01:57 1997
+++ tvscreen.c	Sun Apr 26 20:08:55 1998
@@ -438,12 +438,6 @@
     modes = TV_TRANSFER_STD_IMAGE;
 
     /*  Shared memory extension (TRANSFER_SHMEM_{IMAGE,PIXMAP})  */
-    if ( XShmQueryVersion( s->display, &shm_majv, 
-                           &shm_minv, &shm_pixmaps ) == True ) {
-        modes |= TV_TRANSFER_SHMEM_IMAGE;
-        if ( shm_pixmaps )
-            modes |= TV_TRANSFER_SHMEM_PIXMAP;
-    }
 
     /*  Linear frame buf? (TRANSFER_DIRECT)  */
     S_x_err_count = 0;

--5vNYLRcllDrimb99--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-multimedia" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980426201627.A21132>