All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Limpach <chris@pin.lu>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: anybody using pdb?
Date: Fri, 12 Mar 2004 16:10:49 +0100	[thread overview]
Message-ID: <177501c40845$123fe740$070414ac@pin> (raw)
In-Reply-To: E1B1lDG-00074w-00@wisbech.cl.cam.ac.uk

> Okay, I checked in a fix somewhat like the one you initially
> proposed. Fancy giving it another spin? :-)

Ok, this works.  Thanks!

And breakpoints now work occasionally...  I think the problem is that my
test machine is 2-CPU SMP:
(from a log of the 'wire' between gdb and Xen, Xen->gdb is in [], everything
else is gdb->Xen)
$Mfc510390,1:cc#a5[+][$][O][K][#][9][$][S][a][0]
Here gdb sets the breakpoint by writing 0xcc to the breakpoint address.
Xen then would acknowledge this by replying with OK by sending "+$OK#9a" but
it doesn't get to entirely send the reply since I guess the breakpoint is
hit on the other CPU? (the breakpoint is on __enter_scheduler btw)

The log should look like this:
$Mfc510390,1:cc#a5[+][$][O][K][#][9][a]+$Hc0#db[+][$][O][K][#][9][a]+$C0a#d4
[+][$][S][0][5][#][b][8]+
Here the reply works and gdb sends commands Hc0 and C0a to continue
execution and only then Xen hits the breakpoint and sends $S05#b8 which gdb
then acknowledges with a +...

I guess we'd have to IPI the other CPUs when we hit a breakpoint?

    christian



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

      reply	other threads:[~2004-03-12 15:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-11  0:10 anybody using pdb? Christian Limpach
2004-03-11  8:28 ` Keir Fraser
2004-03-11 17:21   ` Christian Limpach
2004-03-12  7:50     ` Keir Fraser
2004-03-12 11:52     ` Keir Fraser
2004-03-12 15:10       ` Christian Limpach [this message]

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='177501c40845$123fe740$070414ac@pin' \
    --to=chris@pin.lu \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /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.