From owner-freebsd-multimedia  Sun Apr 19 16:48:33 1998
Return-Path: <owner-freebsd-multimedia@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA11865
          for freebsd-multimedia-outgoing; Sun, 19 Apr 1998 16:48:33 -0700 (PDT)
          (envelope-from owner-freebsd-multimedia@FreeBSD.ORG)
Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11832
          for <freebsd-multimedia@FreeBSD.ORG>; Sun, 19 Apr 1998 23:48:27 GMT
          (envelope-from hasty@rah.star-gate.com)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1])
          by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id QAA03334;
          Sun, 19 Apr 1998 16:48:21 -0700 (PDT)
          (envelope-from hasty@rah.star-gate.com)
Message-Id: <199804192348.QAA03334@rah.star-gate.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: tomppa@fidata.fi
cc: freebsd-multimedia@FreeBSD.ORG
Subject: Re: problem capturing video with BT848/Haughpage Win/Tv 
In-reply-to: Your message of "Mon, 20 Apr 1998 02:36:59 +0300."
             <13626.35483.87697.62123@zeta.fidata.fi> 
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Date: Sun, 19 Apr 1998 16:48:21 -0700
From: Amancio Hasty <hasty@rah.star-gate.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id XAA11844
Sender: owner-freebsd-multimedia@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Thats a good clue. Perhaps your shared memory segment is not big enough or
the kernel failed to allocate such a big memory segment.
Play with SHMMAXPGS options...

>From LINT:
options         "SHMMAX=(SHMMAXPGS*PAGE_SIZE+1)"
options         SHMMAXPGS=1025

The other possibility is that your login defaults are too small:

{hasty} limits
Resource limits (current):
  cputime          infinity secs
  filesize         infinity kb
  datasize           524288 kb
  stacksize           65536 kb
  coredumpsize     infinity kb
  memoryuse-cur       32768 kb
  memorylocked     infinity kb
  maxprocesses-cur       64
  openfiles            1000

your /etc/login.conf dictates your limits.

And why you didn't report this earlier??


	Amancio



> 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.
> 
>   Tomppa
> 
> tick:~/src/fxtv/work/fxtv-0.46(11)# gdb ./fxtv
> fxtv       fxtv.core
> tick:~/src/fxtv/work/fxtv-0.46(11)# gdb ./fxtv fxtv.core
> GDB is free software and you are welcome to distribute copies of it
>  under certain conditions; type "show copying" to see the conditions.
> There is absolutely no warranty for GDB; type "show warranty" for
> details.
> GDB 4.16 (i386-unknown-freebsd),
> Copyright 1996 Free Software Foundation, Inc...
> Core was generated by xtv'.
> Program terminated with signal 11, Segmentation fault.
> Cannot access memory at address 0x20039080.
> #0  0x20215562 in ?? ()
> (gdb) bt
> #0  0x20215562 in ?? ()
> #1  0xefbfd6cc in ?? ()
> #2  0xd636 in TVNewFrameHdlr (img=0xefbfd6c8) at tv.c:178
> #3  0xfc4b in TVCAPTUREWorkProc () at tvcapture.c:183
> #4  0xd575 in TVWorkProcTimeoutCB (cl_data=0x0, timer=0xefbfd720) at
> tv.c:141
> #5  0x200e2843 in ?? ()
> #6  0x200e2a14 in ?? ()
> #7  0xf2fa in main (argc=1, argv=0xefbfd7f0) at tv.c:665
> (gdb) q
> tick:~/src/fxtv/work/fxtv-0.46(12)#
> 
> --
> SUN Microsystems Oy PL 102, Niittymäentie 9, 02201 ESPOO, Finland
> Tomi Vainio (System Support Engineer)             +358 9 52556300 hotline
> email: Tomi.Vainio@Sun.COM                        +358 9 52556252 fax



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