Date: Wed, 18 Oct 2006 14:09:20 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: y.pankov@irbis.net.ru Cc: freebsd-multimedia@freebsd.org Subject: Re: FreeBSD DV howto? Message-ID: <20061018.140920.1716873339.imp@bsdimp.com> In-Reply-To: <20061018102300.GB13427@hpc.local> References: <20061017125350.A14616@pkunk.americas.sgi.com> <20061017.140955.1653108615.imp@bsdimp.com> <20061018102300.GB13427@hpc.local>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20061018102300.GB13427@hpc.local>
Yuri Pankov <y.pankov@irbis.net.ru> writes:
: On Tue, Oct 17, 2006 at 02:09:55PM -0600, M. Warner Losh wrote:
: > In message: <20061017125350.A14616@pkunk.americas.sgi.com>
: > Brent Casavant <b.j.casavant@ieee.org> writes:
: > : On Tue, 17 Oct 2006, M. Warner Losh wrote:
: > :
: > : > Like I said, kino gives a bus error when i run it. Like right away,
: > : > before it can even completely paint the screen.
: > :
: > : Ah, I misunderstood. I had run into problems trying to get Kino
: > : to capture from the camera, which is what I assumed you meant. I
: > : didn't realize it was crashing on startup.
: > :
: > : I can't help you much there, other than to note I currently have
: > : Kino working on two different systems (6.0-RELEASE, and 6.1-RELEASE).
: > : If at some point it would help to see a list of my installed ports,
: > : I'd be more than happy to oblige.
: >
: > I've been running bleeding edge current. Maybe I need to do (yet
: > another) portupgrade -avf?
: >
: > Warner
:
: Just a guess: it's uninitialized pointer, caught by malloc debug in -CURRENT (should look like 0x5a5a5a5a5a5a5a... in gdb's output).
: You can try to run Kino with this feature turned off (ln -sf 'aj' /etc/malloc.conf).
Alas, no joy.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061018.140920.1716873339.imp>