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: Thu, 11 Mar 2004 18:21:44 +0100	[thread overview]
Message-ID: <148801c4078d$548e1f80$070414ac@pin> (raw)
In-Reply-To: E1B1LYg-0008Pr-00@wisbech.cl.cam.ac.uk

> I've fixed this a better way, by enabling interrupts before calling
> the pdb handler. Let me know if it still doesn't work.

No it doesn't work, at least not for the "jump to the debugger by pressing
D" case.  Maybe because you only enabled interrupts during traps but not
during interrupts?  AFAICT there's also some locking/flag setting which
might prevent further interrupts while the handler is still running (if I'm
looking at the right code, do_IRQ in xen/arch/i386/irq.c).

I considered enabling interrupts at first but I couldn't exclude re-entrance
issues.  Also I think that it's not the right thing to do in this case:  if
you're using the debugger on Xen, you don't want interrupts enabled.  I
think you'd actually want them explicitly disabled (as opposed to the
previous/current implicit disabling).

   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-11 17:21 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 [this message]
2004-03-12  7:50     ` Keir Fraser
2004-03-12 11:52     ` Keir Fraser
2004-03-12 15:10       ` Christian Limpach

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='148801c4078d$548e1f80$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.