From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <5d45a67da8d55c7b3a956c03e8bef625@mail.gmx.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Zombie-fds
From: "Sascha Retzki" <sretzki@gmx.de>
Date: Fri, 15 Sep 2006 15:06:51 +0200
In-Reply-To: <4e1b45c91d2bbd92af8301817f25f75c@quanstro.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: b5996bfc-ead1-11e9-9d60-3106f5b1d025

> what does ov_open do to the FILE*? (it's pretty confusing to call a FILE* "fd", btw.)

Heh, now that confuses me. A File Deskriptor is a number describing a file, I never made any differences between an int fd and a FILE *fd.  

> 
> why don't you breadcrumb the spaces between fopen/ov_open and ov_open/fclose?
> e,g.
> 	fprint(2, "f->flags = %x; f->fd = %d\n", fp->flags, fp->fd);

What is fp? :-)

> 
> a better way to accompish "isogg" might be to teach file(1) to recognize ogg files.

Actually a good point. Despite I have no idea how file(1) works, I know the word 'magic', I guess it reads some bytes of the file and compares it to entries in some kind of database. The canonical OGG-format has the strings 'ogg ' and 'vorbis' in it, iirc, maybe I give that a shot.

Anyway, as the problem seems to occur with my playvorbis() (also using libvorbis-functions, btw...), too, it does not fix the issue.

You stay correct, tho. Maybe libvorbis does something strange to the FILE *, or, as mentioned in the earlier posts, does use sscanf() or similar.

> 
> - erik