From: Lee Revell <rlrevell@joe-job.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: strace and ALSA ioctls
Date: Thu, 18 May 2006 12:12:06 -0400 [thread overview]
Message-ID: <1147968727.12531.69.camel@mindpipe> (raw)
In-Reply-To: <s5h4pzn2v2r.wl%tiwai@suse.de>
On Thu, 2006-05-18 at 17:47 +0200, Takashi Iwai wrote:
> At Thu, 18 May 2006 11:41:48 -0400,
> Lee Revell wrote:
> >
> > I have never seen strace correctly identify a single ALSA ioctl. This
> > makes debugging a serious PITA. Is it fixable?
>
> Quite unlikely. Some ioctl commands are indeed identical with these
> USBDEVFS_*. This happened since we didn't care about the collision
> and found it too late.
>
> In the kernel side this is no problem because the ioctl cmd is bound
> to each driver's ioctl op. But, from user-space, there is no way to
> distinguish properly.
>
But for some ioctls it says:
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon
echo ...}) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon
echo ...}) = 0
So it seems that strace is aware of some of the collisions but not
others?
Lee
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2006-05-18 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 15:41 strace and ALSA ioctls Lee Revell
2006-05-18 15:47 ` Takashi Iwai
2006-05-18 16:12 ` Lee Revell [this message]
2006-05-18 16:32 ` Takashi Iwai
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=1147968727.12531.69.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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.