From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0000926]: There is no source code for the functions mix_areas1() and mix_areas2() in the file pcm_dmix.c!
Date: Tue, 29 Mar 2005 19:08:30 +0200 [thread overview]
Message-ID: <ff98455ca159173fd93da8d22b84b7ff@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=926>
======================================================================
Reported By: jiyuan
Assigned To:
======================================================================
Project: ALSA - lib
Issue ID: 926
Category: hw specific configuration
Reproducibility: always
Severity: crash
Priority: normal
Status: new
======================================================================
Date Submitted: 02-20-2005 03:18 CET
Last Modified: 03-29-2005 19:08 CEST
======================================================================
Summary: There is no source code for the functions
mix_areas1() and mix_areas2() in the file pcm_dmix.c!
Description:
#warning Please, recode mix_areas1() routine to your architecture...
#warning Please, recode mix_areas2() routine to your architecture...
Therefore, when you using dmix under other architecture CPU, the dmix will
crash down, and make error segmentation fault.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0000824 sparc, powerpc, hppa, alpha, ia64: &quo...
======================================================================
----------------------------------------------------------------------
jdthood - 03-16-05 22:33
----------------------------------------------------------------------
Report https://bugtrack.alsa-project.org/alsa-bug/view.php?id=824 reports the
same bug.
----------------------------------------------------------------------
tiwai - 03-29-05 19:08
----------------------------------------------------------------------
Try the CVS version (better wait until tomorrow).
If you still get segfault, it's not in the part with warnings above.
Possibly, either SYSV shm or semaphore...
Issue History
Date Modified Username Field Change
======================================================================
02-20-05 03:18 jiyuan New Issue
03-16-05 22:33 jdthood Note Added: 0003970
03-17-05 08:16 perex Relationship added related to 0000824
03-29-05 19:08 tiwai Note Added: 0004256
======================================================================
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-03-29 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 17:08 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-17 7:16 [ALSA - lib 0000926]: There is no source code for the functions mix_areas1() and mix_areas2() in the file pcm_dmix.c! bugtrack
2005-03-16 21:33 bugtrack
2005-02-20 2:18 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=ff98455ca159173fd93da8d22b84b7ff@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