From: Paul LeoNerd Evans <leonerd@leonerd.org.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Network code on AMD64
Date: Thu, 21 Jul 2005 22:55:22 +0100 [thread overview]
Message-ID: <20050721215522.GA3558@cel.leo> (raw)
In-Reply-To: <20050721152543.GA4122@jbrown.mylinuxbox.org>
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
On Thu, Jul 21, 2005 at 11:25:43AM -0400, Jim C. Brown wrote:
> > But there's a problem. Currently my only test image is a Windows 98SE
> > install - not best known for being able to properly debug - I shall have
> > to test with a decent Knoppix or something like that... But I find that
> > if I start up IE, it attempts a connection to its default homepage, then
> > Qemu itself segfaults. Normally I'd fire up gdb at this stage and have a
> > good look around, but I gather from documentation that the internals of
> > qemu are far from standard, and I might be somewhat out of my depth here.
I have determined, by the way, a much more precise location for the bug.
I can start a Knoppix image, which can reliably resolve hostnames, and
ping the host machine. I then tried a http-over-telnet, to test TCP. I
connect, send/receive data just fine. The moment I Ctrl+C the telnet,
that's when qemu dies. So I suspect the bug is related to the TCP close
code. I shall investigate further...
--
Paul "LeoNerd" Evans
leonerd@leonerd.org.uk
ICQ# 4135350 | Registered Linux# 179460
http://www.leonerd.org.uk/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-21 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 11:32 [Qemu-devel] Network code on AMD64 Paul LeoNerd Evans
2005-07-21 15:25 ` Jim C. Brown
2005-07-21 16:18 ` Julian Seward
2005-07-21 21:55 ` Paul LeoNerd Evans [this message]
2005-07-21 22:58 ` Paul LeoNerd Evans
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=20050721215522.GA3558@cel.leo \
--to=leonerd@leonerd.org.uk \
--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).