From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LpkaN-0002ZF-Us
	for qemu-devel@nongnu.org; Fri, 03 Apr 2009 10:41:35 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LpkaJ-0002Xc-EM
	for qemu-devel@nongnu.org; Fri, 03 Apr 2009 10:41:35 -0400
Received: from [199.232.76.173] (port=50449 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LpkaJ-0002XZ-An
	for qemu-devel@nongnu.org; Fri, 03 Apr 2009 10:41:31 -0400
Received: from csmtp1.one.com ([195.47.247.21]:35301)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <hans-erik.floryd@rt-labs.com>) id 1LpkaI-0008Sa-Pm
	for qemu-devel@nongnu.org; Fri, 03 Apr 2009 10:41:31 -0400
Received: from [192.168.10.151] (static-213-115-7-226.sme.bredbandsbolaget.se
	[213.115.7.226])
	by csmtp1.one.com (Postfix) with ESMTP id 24C291BC01F08
	for <qemu-devel@nongnu.org>; Fri,  3 Apr 2009 14:41:28 +0000 (UTC)
Message-ID: <49D62089.7030205@rt-labs.com>
Date: Fri, 03 Apr 2009 16:43:21 +0200
From: Hans-Erik Floryd <hans-erik.floryd@rt-labs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] gdbstub not working on Vista
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Hello,

I'm using qemu-system-arm on Vista. It was built using MingW on XP. I am 
hitting the problem reported here:

http://lists.gnu.org/archive/html/qemu-devel/2009-01/msg01871.html

that is, I am unable to connect with gdb because qemu seems to be 
creating an ipv6 socket.

Specifying -p tcp::1234,nowait,nodelay,server,ipv4 fixes the problem.

Enabling socket_debug gives this output (when not using -p above):

inet_listen: getaddrinfo: family ipv6, host ::, port 1234
inet_listen: getaddrinfo: family ipv4, host 0.0.0.0, port 1234
inet_listen: bind(ipv6,::,1234): OK

The patch submitted by Sebastian Herbszt should fix the problem. 
Assuming gdb doesn't support ipv6, is there any reason not to apply the 
patch?

Best regards,
  Hans-Erik Floryd