From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - tools 0000708]: Fix CVS envy24control crash on midi 00 control
Date: Wed, 1 Mar 2006 01:05:09 +0100 [thread overview]
Message-ID: <7438002c8e2bdba02224fd910fde7abc@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=708>
======================================================================
Reported By: shadow
Assigned To:
======================================================================
Project: ALSA - tools
Issue ID: 708
Category: envy24control
Reproducibility: sometimes
Severity: crash
Priority: normal
Status: closed
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 12-05-2004 12:36 CET
Last Modified: 03-01-2006 01:05 CET
======================================================================
Summary: Fix CVS envy24control crash on midi 00 control
Description:
envy24control adds midi support, but if it receives data from a controller
with ID '0' it will crash.
======================================================================
----------------------------------------------------------------------
rlrevell - 12-30-05 03:58
----------------------------------------------------------------------
Is this still broken?
----------------------------------------------------------------------
shadow - 01-11-06 08:24
----------------------------------------------------------------------
I havent used midi function of envy24control in many months. I cannot say
if this issue exists or has been resolved. Please close this report and I
will file a new one if there are problems.
Issue History
Date Modified Username Field Change
======================================================================
12-05-04 12:36 shadow New Issue
12-05-04 12:36 shadow File Added:
cvs_alsa_20041205-envy24control.midi00crash.patch
12-05-04 13:58 shadow Note Added: 0002721
12-05-04 15:02 shadow Note Added: 0002722
12-05-04 15:02 shadow File Added:
cvs_alsa_20041205-envy24control.midi00crash.patch
12-30-05 03:58 rlrevell Note Added: 0007194
12-30-05 04:28 shadow Note Added: 0007209
01-11-06 08:24 shadow Note Edited: 0007209
03-01-06 01:05 rlrevell Status new => closed
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next reply other threads:[~2006-03-01 0:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 0:05 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-30 3:28 [ALSA - tools 0000708]: Fix CVS envy24control crash on midi 00 control bugtrack
2005-12-30 2:58 bugtrack
2004-12-05 14:02 bugtrack
2004-12-05 12:58 bugtrack
2004-12-05 11:36 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=7438002c8e2bdba02224fd910fde7abc@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