9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Sascha Retzki" <sretzki@gmx.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Zombie-fds
Date: Fri, 15 Sep 2006 15:06:51 +0200	[thread overview]
Message-ID: <5d45a67da8d55c7b3a956c03e8bef625@mail.gmx.net> (raw)
In-Reply-To: <4e1b45c91d2bbd92af8301817f25f75c@quanstro.net>

> 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



  reply	other threads:[~2006-09-15 13:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-15 11:30 Sascha Retzki
2006-09-15 11:55 ` erik quanstrom
2006-09-15 12:17   ` Sascha Retzki
2006-09-15 12:55     ` erik quanstrom
2006-09-15 13:06       ` Sascha Retzki [this message]
2006-09-15 13:27         ` erik quanstrom
2006-09-15 12:58     ` Russ Cox
2006-09-15 13:12       ` Sascha Retzki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5d45a67da8d55c7b3a956c03e8bef625@mail.gmx.net \
    --to=sretzki@gmx.de \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).