From: Takashi Iwai <tiwai@suse.de>
To: "M. Ritscher" <mr203010spam@gmx.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: libasound dies on snd_pcm_open
Date: Wed, 12 Feb 2003 19:18:14 +0100 [thread overview]
Message-ID: <s5hd6lxmkgp.wl@alsa2.suse.de> (raw)
In-Reply-To: <200302121848.23717.mr203010spam@gmx.net>
At Wed, 12 Feb 2003 18:48:12 +0100,
M. Ritscher <mr203010spam@gmx.net> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi again,
>
> On Tuesday 11 February 2003 21:47, M. Ritscher wrote:
> > Stopped due to shared library event.
> >
> I've now compiled a version of libasound with debug enabled and found out that
> it dies on me on line 61 of dlmisc.c
> Stopped due to shared library event.
>
> ===========================
> void *snd_dlopen(const char *name, int mode)
> {
> <cut>
> ###>>> return dlopen(name, mode);
> }
> ============================
>
> name: "/usr/lib/libasound.so.2 (which correctly links to libasound.so.2.0.0)
> mode: 2
>
> I've played around with my code a bit and have tried to reduce it to a
> minimum, still, no luck.
> ============================================
> int KCorrView::openNewALSADev(){
> snd_pcm_t *capture_hd;
> int err = 0;
>
> if ((err = snd_pcm_open(&capture_hd,
> "hwplug:0,0", SND_PCM_STREAM_CAPTURE, 0)) < 0) {
^^^^^^
is this correct? not "plughw:0,0" ?
Takashi
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next prev parent reply other threads:[~2003-02-12 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 20:47 libasound dies on snd_pcm_open M. Ritscher
2003-02-12 17:48 ` M. Ritscher
2003-02-12 18:18 ` Takashi Iwai [this message]
2003-02-12 22:38 ` M. Ritscher
2003-02-13 20:37 ` M. Ritscher
2003-02-13 21:00 ` Jaroslav Kysela
2003-02-14 7:00 ` mr203010spam
2003-02-14 14:44 ` M. Ritscher
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=s5hd6lxmkgp.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=mr203010spam@gmx.net \
/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.