From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0002287]: Segfaults all functions after snd_pcm_hw_params_get_buffer_size (params,(snd_pcm_uframes_t *) & val);
Date: Fri, 21 Jul 2006 01:28:43 +0200 [thread overview]
Message-ID: <5c7721ab8d8830ad4c80d61dd231c19e@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2287>
======================================================================
Reported By: cruiseoveride
Assigned To:
======================================================================
Project: ALSA - lib
Issue ID: 2287
Category: 0_general
Reproducibility: always
Severity: crash
Priority: normal
Status: new
======================================================================
Date Submitted: 07-16-2006 18:03 CEST
Last Modified: 07-21-2006 01:28 CEST
======================================================================
Summary: Segfaults all functions after
snd_pcm_hw_params_get_buffer_size (params,(snd_pcm_uframes_t *) & val);
Description:
I am new to Alsa and am not happy at all at the state of documentation
available.
You guys seriously need to do something about this.
I have an M-Audio Audiophile Delta 192 (ICE1724) and I want to port
envy24control for this chip, However I first need to familiar myself with
the ALSA API. So I began by looking for simple examples on how to use ALSA
API and came accross the followinf prog (Attached file test.c).
The program compiles cleanly with gcc-4.1 and runs, however after it
prints out the ..."buffer size = 8192 frames"
It segfaults.
If you slash out line 104, it resolves the issue.
My question is,
Is there a bug in this function?
Code was obtained from http://www.linuxjournal.com/article/6735
======================================================================
----------------------------------------------------------------------
cruiseoveride - 07-21-06 01:16
----------------------------------------------------------------------
ok i put the pics of my card here
http://cruise.homeunix.net/temp/
the canera is not great but u can see three AKMs
I am trying to find a matching ESI.
----------------------------------------------------------------------
cruiseoveride - 07-21-06 01:28
----------------------------------------------------------------------
The pics might not be too clear soo this is wats on the AKMs
AKM
AK5385AVP
026D0603N
AKM
AK4358VQ
0551JBK
AKM
AK4114VQ
0522JBK
Hope this helps
Issue History
Date Modified Username Field Change
======================================================================
07-16-06 18:03 cruiseoveride New Issue
07-16-06 18:03 cruiseoveride File Added: test.c
07-16-06 20:38 cruiseoveride Issue Monitored: cruiseoveride
07-17-06 02:44 Raymond Note Added: 0011032
07-17-06 02:47 Raymond Note Edited: 0011032
07-17-06 03:18 Raymond Note Edited: 0011032
07-17-06 05:45 cruiseoveride Note Added: 0011033
07-17-06 05:46 cruiseoveride Note Edited: 0011033
07-17-06 07:31 Raymond Note Added: 0011035
07-17-06 08:23 Raymond Note Added: 0011036
07-17-06 08:26 Raymond Note Edited: 0011036
07-17-06 14:48 cruiseoveride Note Added: 0011039
07-17-06 14:59 cruiseoveride Note Added: 0011040
07-17-06 16:07 Raymond Note Added: 0011042
07-17-06 16:31 Raymond Note Edited: 0011042
07-17-06 16:40 cruiseoveride Note Added: 0011044
07-17-06 17:13 cruiseoveride Note Added: 0011045
07-17-06 17:34 Raymond Note Added: 0011046
07-17-06 17:56 cruiseoveride Note Added: 0011047
07-18-06 07:44 Raymond Note Added: 0011053
07-18-06 14:21 cruiseoveride Note Added: 0011057
07-18-06 14:35 Raymond Note Added: 0011060
07-19-06 02:52 cruiseoveride Note Added: 0011075
07-19-06 03:27 Raymond Note Added: 0011076
07-19-06 06:21 Raymond Note Added: 0011080
07-19-06 17:43 cruiseoveride Note Added: 0011090
07-19-06 17:50 cruiseoveride File Added: chip.jpg
07-20-06 04:22 Raymond Note Added: 0011107
07-20-06 05:01 Raymond Note Edited: 0011107
07-20-06 08:05 cruiseoveride Note Added: 0011112
07-20-06 08:19 Raymond Note Added: 0011114
07-20-06 08:22 Raymond Note Edited: 0011114
07-20-06 10:49 Raymond Note Added: 0011116
07-20-06 15:52 cruiseoveride Note Added: 0011127
07-20-06 16:09 Raymond Note Added: 0011130
07-20-06 16:12 Raymond Note Added: 0011131
07-20-06 16:35 cruiseoveride Note Added: 0011132
07-20-06 16:39 cruiseoveride Note Edited: 0011132
07-20-06 17:42 cruiseoveride Note Added: 0011134
07-20-06 17:49 Raymond Note Added: 0011135
07-20-06 17:55 Raymond Note Edited: 0011135
07-20-06 19:30 Raymond Note Added: 0011136
07-20-06 19:31 Raymond Note Edited: 0011136
07-21-06 01:16 cruiseoveride Note Added: 0011138
07-21-06 01:28 cruiseoveride Note Added: 0011139
======================================================================
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next reply other threads:[~2006-07-20 23:28 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-20 23:28 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-06 3:26 [ALSA - lib 0002287]: Segfaults all functions after snd_pcm_hw_params_get_buffer_size (params,(snd_pcm_uframes_t *) & val); bugtrack
2006-08-06 2:46 bugtrack
2006-08-06 2:17 bugtrack
2006-08-06 1:58 bugtrack
2006-08-06 1:54 bugtrack
2006-08-06 1:25 bugtrack
2006-08-06 1:16 bugtrack
2006-08-06 0:31 bugtrack
2006-08-05 21:17 bugtrack
2006-08-05 0:50 bugtrack
2006-08-05 0:10 bugtrack
2006-08-01 2:56 bugtrack
2006-08-01 2:00 bugtrack
2006-08-01 1:22 bugtrack
2006-07-31 23:49 bugtrack
2006-07-31 23:42 bugtrack
2006-07-31 23:26 bugtrack
2006-07-30 4:26 bugtrack
2006-07-30 3:59 bugtrack
2006-07-27 8:24 bugtrack
2006-07-27 5:15 bugtrack
2006-07-27 4:38 bugtrack
2006-07-27 4:25 bugtrack
2006-07-27 2:43 bugtrack
2006-07-26 23:03 bugtrack
2006-07-26 23:00 bugtrack
2006-07-26 22:57 bugtrack
2006-07-26 22:54 bugtrack
2006-07-26 22:15 bugtrack
2006-07-26 21:59 bugtrack
2006-07-26 13:42 bugtrack
2006-07-26 5:46 bugtrack
2006-07-26 4:22 bugtrack
2006-07-26 2:53 bugtrack
2006-07-26 2:47 bugtrack
2006-07-26 2:41 bugtrack
2006-07-26 2:30 bugtrack
2006-07-25 23:20 bugtrack
2006-07-25 22:19 bugtrack
2006-07-25 16:02 bugtrack
2006-07-24 0:15 bugtrack
2006-07-23 16:27 bugtrack
2006-07-23 16:03 bugtrack
2006-07-23 15:57 bugtrack
2006-07-23 15:49 bugtrack
2006-07-23 15:39 bugtrack
2006-07-23 15:23 bugtrack
2006-07-23 12:16 bugtrack
2006-07-23 4:41 bugtrack
2006-07-23 4:26 bugtrack
2006-07-23 2:05 bugtrack
2006-07-22 2:12 bugtrack
2006-07-22 1:00 bugtrack
2006-07-22 0:13 bugtrack
2006-07-21 18:23 bugtrack
2006-07-21 1:28 bugtrack
2006-07-20 23:45 bugtrack
2006-07-20 23:16 bugtrack
2006-07-20 17:30 bugtrack
2006-07-20 15:49 bugtrack
2006-07-20 15:42 bugtrack
2006-07-20 14:35 bugtrack
2006-07-20 14:12 bugtrack
2006-07-20 14:09 bugtrack
2006-07-20 13:52 bugtrack
2006-07-20 8:49 bugtrack
2006-07-20 6:19 bugtrack
2006-07-20 6:05 bugtrack
2006-07-20 2:22 bugtrack
2006-07-19 15:43 bugtrack
2006-07-19 4:21 bugtrack
2006-07-19 1:27 bugtrack
2006-07-19 0:52 bugtrack
2006-07-18 12:35 bugtrack
2006-07-18 12:21 bugtrack
2006-07-18 5:44 bugtrack
2006-07-17 15:56 bugtrack
2006-07-17 15:34 bugtrack
2006-07-17 15:13 bugtrack
2006-07-17 14:40 bugtrack
2006-07-17 14:07 bugtrack
2006-07-17 12:59 bugtrack
2006-07-17 12:48 bugtrack
2006-07-17 6:23 bugtrack
2006-07-17 5:31 bugtrack
2006-07-17 3:45 bugtrack
2006-07-17 0:44 bugtrack
2006-07-16 16:03 bugtrack
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=5c7721ab8d8830ad4c80d61dd231c19e@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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