All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jonathan M. McCune" <jonmccune@cmu.edu>
To: xen-devel@lists.xensource.com
Cc: bparno@ece.cmu.edu, Arvind Seshadri <arvinds@cs.cmu.edu>
Subject: gdbserver-xen / gdb crashing domU
Date: Tue, 27 Sep 2005 18:49:06 -0400	[thread overview]
Message-ID: <4339CC62.4040102@cmu.edu> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1173 bytes --]

Hello,

I'm trying to use gdb and gdbserver-xen to walk through the instructions 
executed when starting up a domU kernel.  We are using the current 
xen-unstable (linux-2.6.12-xenU).  I have followed the instructions in 
tools/debugger/gdb/ and I am able to successfully attach to a running 
domU kernel.  I have compiled the domU kernel with debug options as 
described in tools/debugger/gdb/README.  After attaching to the running 
domU kernel, I observe the following behavior:

Issuing the gdb commands 'step', 'stepi', 'next', and 'nexti' when the 
domU kernel is initially paused all crash the domU kernel silently 
(i.e., the state of said domU goes to 'c' if you issue an `xm list` in 
dom0).  'continue' causes the domU kernel to boot up correctly.

All the breakpoints I've tried setting so far (setting the breakpoints 
before issuing the 'continue' in gdb) cause the domU kernel to panic 
when the function at which the breakpoint is set gets run.  Functions 
I've tried setting breakpoints for include dup_task_struct, queue_work, 
scheduler_tick, and activate_task.

Is it possible to step through the domU kernel code as it is booted in Xen?

Thanks,
-Jon


[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3170 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

             reply	other threads:[~2005-09-27 22:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27 22:49 Jonathan M. McCune [this message]
2005-09-28  1:59 ` gdbserver-xen / gdb crashing domU Kip Macy
2005-09-28 14:32   ` Jonathan M. McCune
2005-09-28 18:48     ` Kip Macy
     [not found] <AcXD0FxHkvtyx4KaRKO323jkm7Ws5wASBRVA>
2005-09-28 10:37 ` Ian Pratt
2005-09-28 18:50   ` Kip Macy

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=4339CC62.4040102@cmu.edu \
    --to=jonmccune@cmu.edu \
    --cc=arvinds@cs.cmu.edu \
    --cc=bparno@ece.cmu.edu \
    --cc=xen-devel@lists.xensource.com \
    /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.