From: David Woodhouse <dwmw2@infradead.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] do_accept() fix.
Date: Sun, 10 Dec 2006 23:36:36 +0000 [thread overview]
Message-ID: <1165793796.3650.22.camel@shinybook.infradead.org> (raw)
With this on top of the NPTL support I posted yesterday, I finally have
nspluginwrapper running the i386 flash plugin inside firefox on my PPC
laptop -- to a certain extent.
Index: linux-user/syscall.c
===================================================================
RCS file: /cvsroot/qemu/qemu/linux-user/syscall.c,v
retrieving revision 1.78
diff -u -p -r1.78 syscall.c
--- linux-user/syscall.c 8 Dec 2006 01:32:58 -0000 1.78
+++ linux-user/syscall.c 10 Dec 2006 23:32:48 -0000
@@ -841,7 +842,7 @@ static long do_accept(int fd, target_ulo
target_ulong target_addrlen)
{
socklen_t addrlen = tget32(target_addrlen);
- void *addr = alloca(target_addrlen);
+ void *addr = alloca(addrlen);
long ret;
ret = get_errno(accept(fd, addr, &addrlen));
--
dwmw2
reply other threads:[~2006-12-10 23:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1165793796.3650.22.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--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).