All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eddie Kohler <kohler@cs.ucla.edu>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] i386 debugging stubs: Consider segment bases
Date: Sat, 25 Sep 2010 01:35:39 -0700	[thread overview]
Message-ID: <4C9DB45B.7080609@cs.ucla.edu> (raw)
In-Reply-To: <4C9DA344.5010702@web.de>

Thanks for the response.  I agree the patch is a workaround, but it is a 
useful workaround, and I'd still argue for including it.

The patch doesn't *require* that CS.base == DS.base.  Breakpoints 
correctly and exclusively use CS.base.  However, any memory examination 
uses DS.base, and you're right that the user might "want" to examine 
some other segment.  A GDB fix would involve changing the gdb remote 
protocol as well as GDB itself and the GDB user interface.  Google says 
you've been thinking about that for a while now -- is it going well?

> For the time being, you should be able to workaround the gdb limitation
> by setting two breakpoints: one on the linear address and another one on
> the CS offset. Not nice, but used to work for us.

I don't mind the double-breakpoint as much, but memory examination would 
still be broken, yes?

I don't understand the comment about "prevents setting breakpoints on 
inactive segments."  The code for setting breakpoints has not changed.

Do you think the patch would actually make debugging WORSE on any OS? 
Or have any other undesirable effects, or make it harder to DTRT when 
GDB is ready?  It seems safe & useful to me; & it's 2 LOC!

Eddie

  reply	other threads:[~2010-09-25  8:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-25  0:25 [Qemu-devel] [PATCH] i386 debugging stubs: Consider segment bases Eddie Kohler
2010-09-25  7:22 ` [Qemu-devel] " Jan Kiszka
2010-09-25  8:35   ` Eddie Kohler [this message]
2010-09-26  6:44     ` Jan Kiszka
2010-09-26 17:19       ` Eddie Kohler
2010-09-27  6:29         ` Jan Kiszka

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=4C9DB45B.7080609@cs.ucla.edu \
    --to=kohler@cs.ucla.edu \
    --cc=jan.kiszka@web.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.