From: malc <av1474@comtv.ru>
To: Mark McLoughlin <markmc@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Justin M. Forbes" <jforbes@redhat.com>,
Gene Czarcinski <gene@czarc.net>
Subject: Re: [Qemu-devel] Re: audio segfault in qemu-kvm-0.11.0
Date: Fri, 23 Oct 2009 17:41:38 +0400 (MSD) [thread overview]
Message-ID: <Pine.LNX.4.64.0910231739270.2740@linmac.oyster.ru> (raw)
In-Reply-To: <Pine.LNX.4.64.0910231729590.2663@linmac.oyster.ru>
On Fri, 23 Oct 2009, malc wrote:
> On Fri, 23 Oct 2009, Mark McLoughlin wrote:
>
> > Hi,
> >
> > Any ideas on this segfault a Fedora 12 user (Gene, cc-ed) is seeing?
[..snip..]
>
> Summary: No idea.
>
FWIW, there's no information whatosever about what audio hardware was
built and enabled, what sound system was used on the host/guest the
report is devoid of any useful information (given the state of the
backtrace)
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2009-10-23 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 13:16 [Qemu-devel] audio segfault in qemu-kvm-0.11.0 Mark McLoughlin
2009-10-23 13:31 ` [Qemu-devel] " malc
2009-10-23 13:41 ` malc [this message]
2009-10-23 13:50 ` Mark McLoughlin
2009-10-23 14:29 ` malc
2009-10-23 15:11 ` Gene Czarcinski
2009-10-23 17:34 ` malc
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=Pine.LNX.4.64.0910231739270.2740@linmac.oyster.ru \
--to=av1474@comtv.ru \
--cc=gene@czarc.net \
--cc=jforbes@redhat.com \
--cc=markmc@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).