From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: Sending 0xFx events causes libasound to segfault
Date: Fri, 29 Mar 2024 21:18:18 +0100 (CET) [thread overview]
Message-ID: <20240329201818.AF9CCF8025F@alsa1.perex.cz> (raw)
In-Reply-To: <1711743496459402084-webhooks-bot@alsa-project.org>
alsa-project/alsa-lib issue #392 was edited from human222:
ALSA 1.1.9. This issue breaks DOSBox-X MIDI playback.
Discovered through this thread: https://github.com/joncampbell123/dosbox-x/issues/4873
In particular, this comment: https://github.com/joncampbell123/dosbox-x/issues/4873#issuecomment-2026694848
Issue URL : https://github.com/alsa-project/alsa-lib/issues/392
Repository URL: https://github.com/alsa-project/alsa-lib
next parent reply other threads:[~2024-03-29 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1711743496459402084-webhooks-bot@alsa-project.org>
2024-03-29 20:18 ` GitHub issues - edited [this message]
[not found] <1711743175606406689-webhooks-bot@alsa-project.org>
2024-03-29 20:12 ` Sending 0xFx events causes libasound to segfault GitHub issues - opened
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=20240329201818.AF9CCF8025F@alsa1.perex.cz \
--to=github@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