All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [5743] gdbstub: manage CPUs as threads (Jan Kiszka)
Date: Tue, 18 Nov 2008 21:20:52 +0000	[thread overview]
Message-ID: <200811182120.53504.paul@codesourcery.com> (raw)
In-Reply-To: <49232A03.3000100@codemonkey.ws>

On Tuesday 18 November 2008, Anthony Liguori wrote:
> Paul Brook wrote:
> > On Tuesday 18 November 2008, Anthony Liguori wrote:
> >> Revision: 5743
> >>           http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=5743
> >> Author:   aliguori
> >> Date:     2008-11-18 20:30:24 +0000 (Tue, 18 Nov 2008)
> >>
> >> Log Message:
> >> -----------
> >> gdbstub: manage CPUs as threads (Jan Kiszka)
> >
> > This is wrong. CPUs do not share the same address space, so should be
> > modelled as processes, not threads.
>
> They share the same physical address space.  

GDB works with virtual address spaces. Each CPU has its own MMU, so as soon as 
you load a multitasking OS the chances are that these will look significantly 
different.

> How well does GDB support 
> debugging processes verses threads?  A cursory look seems to suggest the
> thread debugging support is slightly better (thread events) than the
> process debugging support.  They look very similar though.

The thread model can't describe what's actually happening. gdb multiprocess 
support definitely exists (and if it doesn't work right now it's being 
actively worked on), so we should use it.

Paul

  parent reply	other threads:[~2008-11-18 21:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-18 20:30 [Qemu-devel] [5743] gdbstub: manage CPUs as threads (Jan Kiszka) Anthony Liguori
2008-11-18 20:42 ` Paul Brook
2008-11-18 20:48   ` Anthony Liguori
2008-11-18 21:00     ` François Revol
2008-11-18 21:20     ` Paul Brook [this message]
2008-11-18 22:27       ` [Qemu-devel] " 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=200811182120.53504.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=anthony@codemonkey.ws \
    --cc=jan.kiszka@siemens.com \
    --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.