From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Paul Davis <paul@linuxaudiosystems.com>,
Dan Tihelka <dtihelka@kky.zcu.cz>,
alsa-devel@lists.sourceforge.net
Subject: Re: Build-in mixer
Date: Fri, 17 Oct 2003 13:13:14 +0200 [thread overview]
Message-ID: <s5had80f779.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.53.0310170938390.1221@pnote.perex-int.cz>
At Fri, 17 Oct 2003 09:41:27 +0200 (CEST),
Jaroslav wrote:
>
> On Wed, 15 Oct 2003, Takashi Iwai wrote:
>
> > At Wed, 15 Oct 2003 10:53:51 -0400,
> > Paul Davis wrote:
> > >
> > > >it's not related with threads, but it invokes a fork for a server
> > > >process (a main control only, doesn't do mixing stuffs).
> > > >it looks like there is something wrong with this together with xmms.
> > > >i've seen that Xlib got a spurious async.
> > > >magically enough, the attached patch seems to fix.
> > >
> > > >From http://www.gtk.org/faq/#AEN477
> > >
> > > ----------------------------------------------------------------------
> > > 5.5. Why does this strange 'x io error' occur when I fork() in my GTK+ app?
> > > Why does this strange 'x io error' occur when I fork() in my GTK+ app?
> > >
> > > This is not really a GTK+ problem, and the problem is not related to
> > > fork() either. If the 'x io error' occurs then you probably use the
> > > exit() function in order to exit from the child process.
> > >
> > > When GDK opens an X display, it creates a socket file descriptor. When
> > > you use the exit() function, you implicitly close all the open file
> > > descriptors, and the underlying X library really doesn't like this.
> > >
> > > The right function to use here is _exit().
> >
> > oh yeah, that's it. replacing two exit() calls in pcm_direct.c with
> > _exit() fixes the problem indeed.
> > thanks for the info!
>
> I think that only one replacement makes sense - in
> snd_pcm_direct_server_create(). Fixed in CVS now.
hmm, it looks like server_job() needs _exit(), too.
i got an error
Gdk-ERROR **: Fatal IO error 9 (Bad file descriptor) on X server :0.0.
when i stop the playback with xmms-alsa.
replacing exit() with _exit() fixes the error.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
next prev parent reply other threads:[~2003-10-17 11:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 8:24 Build-in mixer Dan Tihelka
2003-10-08 11:24 ` Paul Davis
2003-10-08 12:04 ` Takashi Iwai
2003-10-10 8:41 ` Dan Tihelka
2003-10-11 15:33 ` Daniel Tihelka
2003-10-12 16:44 ` Frank Barknecht
2003-10-14 7:39 ` Dan Tihelka
2003-10-14 11:34 ` Paul Davis
2003-10-15 9:15 ` Dan Tihelka
2003-10-15 11:24 ` Paul Davis
2003-10-15 12:10 ` Dan Tihelka
2003-10-15 12:40 ` Paul Davis
2003-10-15 14:19 ` Takashi Iwai
2003-10-15 14:53 ` Paul Davis
2003-10-15 15:01 ` Takashi Iwai
2003-10-15 15:31 ` Takashi Iwai
2003-10-17 7:41 ` Jaroslav Kysela
2003-10-17 11:13 ` Takashi Iwai [this message]
2003-10-17 7:31 ` Jaroslav Kysela
2003-10-17 7:28 ` Jaroslav Kysela
2003-10-13 12:13 ` Clemens Ladisch
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=s5had80f779.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=dtihelka@kky.zcu.cz \
--cc=paul@linuxaudiosystems.com \
--cc=perex@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.