qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Andreas Schultz <aschultz@warp10.net>,
	Jan Kiszka <jan.kiszka@web.de>,
	kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: gdbstub: packet reply is too long
Date: Sat, 20 Dec 2008 21:34:00 +0000	[thread overview]
Message-ID: <200812202134.01169.paul@codesourcery.com> (raw)
In-Reply-To: <494D620A.8020102@web.de>

> >> From a higher perspective, it is surely not the cleanest approach. But
> >> it still appears to be the only one which helps us working around this
> >> gdb shortcoming.
> >
> > Actually it isn't. You could add an explicit switch.
>
> And what would this buy us? I would have to go from your gdb terminal to
> qemu, probably the monitor, just to switch manually what now happens
> automatically. I don't see the case where you wouldn't want to switch
> when you try to debug 16 or 32 bit code, so what would be the gain? Or
> do you want some switch to disable this automatic register format
> switching?

Because, as I've said several times before, the "automatic switching" is 
wrong. It may happen to work in your very limited circumstances, but there 
are many fairly common circumstances (e.g. stepping between a 64-bit kernel 
and a 32-bit userspace) where it's just plain broken. I object strongly to 
a "fix" that prevents a proper gdb from working.

> There are internal issues in gdb (hard coupling of current and target
> arch) that will not allow this to be fixed in the near future

Really? I'm pretty sure other architectures already manage it.

Paul

  reply	other threads:[~2008-12-20 21:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1229776952.22890.2.camel@ws-aschultz>
2008-12-20 15:49 ` [Qemu-devel] Re: gdbstub: packet reply is too long Jan Kiszka
2008-12-20 20:35   ` Paul Brook
2008-12-20 21:00     ` Jan Kiszka
2008-12-20 21:03       ` Paul Brook
2008-12-20 21:22         ` Jan Kiszka
2008-12-20 21:34           ` Paul Brook [this message]
2008-12-20 21:55             ` Jan Kiszka
2008-12-20 22:08               ` Paul Brook
2008-12-20 22:34                 ` Jan Kiszka
2008-12-20 22:46                   ` Paul Brook
2008-12-20 23:44                     ` Jan Kiszka
2008-12-26 23:30                       ` Daniel Jacobowitz
2008-12-29 14:58                         ` Jan Kiszka
2008-12-30 22:43                           ` Daniel Jacobowitz
2009-01-02 12:53                             ` Jan Kiszka
2009-01-03  1:53                               ` Jamie Lokier
2009-01-04 13:50                                 ` 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=200812202134.01169.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=aschultz@warp10.net \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --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).