From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=51876 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OOnEO-0005EB-75 for qemu-devel@nongnu.org; Wed, 16 Jun 2010 03:40:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OOnEM-0004Wl-Oh for qemu-devel@nongnu.org; Wed, 16 Jun 2010 03:40:16 -0400 Received: from fmmailgate03.web.de ([217.72.192.234]:55783) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OOnEM-0004WR-Ce for qemu-devel@nongnu.org; Wed, 16 Jun 2010 03:40:14 -0400 Message-ID: <4C187FD7.5080601@web.de> Date: Wed, 16 Jun 2010 09:40:07 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <20100516152304.10489.35592.malonedeb@potassium.ubuntu.com> <20100616070748.20899.45040.malone@wampee.canonical.com> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig56E85E5F67810DB0B7CDAFBA" Sender: jan.kiszka@web.de Subject: [Qemu-devel] Re: [Bug 581353] Re: qemu doesn't stop execution upon hitting a breakpoint List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jun Koi Cc: chimeranet89@gmail.com, qemu-devel@nongnu.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig56E85E5F67810DB0B7CDAFBA Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Jun Koi wrote: > On Wed, Jun 16, 2010 at 4:07 PM, Alfredo Mungo = wrote: >> Same thing happens to me, same versions as above.. I must turn to >> another app to accomplish my work while awaiting for a bug-fix, the co= de >> is perfectly executed but while gdb hits the breakpoints qemu goes on.= =2E >> >> -- >> qemu doesn't stop execution upon hitting a breakpoint >> https://bugs.launchpad.net/bugs/581353 >> You received this bug notification because you are a member of qemu- >> devel-ml, which is subscribed to QEMU. >=20 > i think this bug has been fixed in 0.12.4. have you tried that?? Or this is a well-known gdb deficit: if the bootloader operates in real-mode, you have to set two breakpoints, one at the linear address to make qemu catch it, and another one at the segment offset to avoid gdb skipping the exit due to ip !=3D bp-addr. gdb is still fairly restricted when it comes to system-level debugging, specifically as it lacks support for special x86 registers and the segmented addressing mode. Jan --------------enig56E85E5F67810DB0B7CDAFBA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkwYf9sACgkQitSsb3rl5xTG/QCdGftP9x2oiMzj8gsh/4zXAIbc WvwAoMK8abjYF58fXdcFRmDYWvb1dAvy =RnnL -----END PGP SIGNATURE----- --------------enig56E85E5F67810DB0B7CDAFBA--