qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian MICHON <christian.michon@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] pcnet/mingw32 debug info (help needed)
Date: Fri, 22 Jul 2005 09:31:51 +0200	[thread overview]
Message-ID: <46d6db660507220031588860a5@mail.gmail.com> (raw)

Apparently, the crash I'm getting is from the tcp/ip layer inside
mingw libs (without debug info). libws2 to be more accurate.
(Maybe it's a slirp/pcnet incompatibility ?)

here's the output of gdb. If anyone can make something from it,
thanks in advance. Pls note I also did a comparison on the
preprocessed output of pcnet.c between linux hosts and
windows host, and htonl calls was the only difference (I
realigned it, but it fails the same way).

==========================================================
$ gdb qemu.exe 
GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-mingw32"...
(gdb) set args -L . -cdrom slaxpro.iso -nic-pcnet
(gdb) run
Starting program: qemu.exe -L . -cdrom slaxpro.iso -nic-pcnet

Program received signal SIGSEGV, Segmentation fault.
0x77fa5575 in _libws2_32_a_iname ()
(gdb) where
#0  0x77fa5575 in _libws2_32_a_iname ()
#1  0x00000000 in ?? ()
==========================================================

-- 
Christian

             reply	other threads:[~2005-07-22  7:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-22  7:31 Christian MICHON [this message]
2005-07-22 10:30 ` [Qemu-devel] pcnet/mingw32 debug info (help needed) Kazu
2005-07-22 12:52   ` Christian MICHON
2005-07-23  2:05     ` Kazu

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=46d6db660507220031588860a5@mail.gmail.com \
    --to=christian.michon@gmail.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).