From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1Cg2Qx-0004dx-FT for qemu-devel@nongnu.org; Sun, 19 Dec 2004 09:53:19 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1Cg2Qq-0004a4-5B for qemu-devel@nongnu.org; Sun, 19 Dec 2004 09:53:13 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Cg2Qp-0004a0-F3 for qemu-devel@nongnu.org; Sun, 19 Dec 2004 09:53:11 -0500 Received: from [216.99.193.136] (helo=jade.spiritone.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1Cg2AU-0003wM-I3 for qemu-devel@nongnu.org; Sun, 19 Dec 2004 09:36:18 -0500 Received: from [192.168.0.2] (216-99-213-225.dsl.aracnet.com [216.99.213.225]) (authenticated bits=0) by jade.spiritone.com (8.12.8/8.12.8) with ESMTP id iBJEaHMD030211 for ; Sun, 19 Dec 2004 06:36:17 -0800 Message-ID: <41C591AD.3060603@BitWagon.com> Date: Sun, 19 Dec 2004 06:35:25 -0800 From: John Reiser MIME-Version: 1.0 Subject: Re: [Qemu-devel] qemu on Fedora Core 3 (Linux 2.6.9+), glibc-2.3.3 References: <41C50D64.7070209@BitWagon.com> <41e41e7a04121902033c7a42ee@mail.gmail.com> <41C58841.4060008@BitWagon.com> In-Reply-To: <41C58841.4060008@BitWagon.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org This optional part of the patch to vl.c: ----- @@ -3449,6 +3455,7 @@ exit(1); } else { printf("Waiting gdb connection on port %d\n", gdbstub_port); +sleep(5); } } else #endif ----- resulted from my misunderstanding of what qemu actually does. I interpreted "Waiting" as a synchronizing rendezvous blocking wait, while it seems that qemu is merely "Listening" without blocking. The difference is important to me because I want to observe the very first emulated instruction at hardware boot. For the moment, I have put an infinite loop there, then advance the instruction pointer by hand once the gdb connection is established. --