From: "Jonathan M. McCune" <jonmccune@cmu.edu>
To: Kip Macy <kip.macy@gmail.com>
Cc: NAHieu <nahieu@gmail.com>, Arvind Seshadri <arvinds@cs.cmu.edu>,
xen-devel@lists.xensource.com, Bryan Parno <parno@cmu.edu>
Subject: Re: pdb missing files?
Date: Fri, 30 Sep 2005 17:11:17 -0400 [thread overview]
Message-ID: <433DA9F5.6060609@cmu.edu> (raw)
In-Reply-To: <b1fa29170509301349x3e31b1a8r9d132d3d12ae4699@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1711 bytes --]
Hi Kip,
Yes, that's exactly my line 394.
And, just for completeness,
root:05:10 PM:root $ ./gdbserver-xen 127.0.0.1:9999 --attach 10
dom0 op failed: No such process
Cannot attach to domain 10: Illegal seek (29)
Thanks,
-Jon
Kip Macy wrote:
>>The next obstacle is that gdbserver-xen is segfaulting upon connection
>>from gdb in dom0. Again, this works great with an unmodified domU. You
>>asked me to give the output from the two different runs of gdbserver-xen.
>>
>>
>
>
>I actually meant when you gave it an invalid domain id, but that isn't a key
>issue ...
>
>
>#0 0x40021fb4 in map_domain_va () from /usr/lib/libxenctrl.so.3.0
>
>
>>(gdb) bt
>>#0 0x40021fb4 in map_domain_va () from /usr/lib/libxenctrl.so.3.0
>>#1 0x4002268a in xc_ptrace () from /usr/lib/libxenctrl.so.3.0
>>#2 0x0804cb27 in linux_read_memory (memaddr=0, myaddr=0xbff5ab50 "",
>>len=8)
>>at ../../../gdb-6.2.1/gdb/gdbserver/linux-xen-low.c:394
>>#3 0x0804bd41 in read_inferior_memory (memaddr=The value of variable
>>'memaddr' is distributed across several
>>locations, and GDB cannot access its value.
>>
>>
>
>
>That is a rather strange place for it to be blowing up. In the past there
>were cases where it would blow up in xc_ptrace when it tried to dereference
>an address that had not been successfully mapped to. In principle using
>alloca could bite you if len were so long that you ran off your stack, but
>you have a small stack and you're only reading 8 bytes. I'll see if I can
>determine any more by spelunking at the assembly level.
>
>Just to confirm that I'm looking at the same code, is your line 394:
>
>buffer[i] = myptrace (xc_handle, PTRACE_PEEKTEXT, inferior_pid,
>(PTRACE_ARG3_TYPE) addr, 0);
>
>
[-- 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
next prev parent reply other threads:[~2005-09-30 21:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 5:58 pdb missing files? Jonathan M. McCune
2005-09-30 6:13 ` Kip Macy
2005-09-30 6:27 ` Jonathan McCune
2005-09-30 6:42 ` Kip Macy
2005-09-30 7:04 ` Jonathan McCune
2005-09-30 7:16 ` Kip Macy
2005-09-30 7:26 ` NAHieu
2005-09-30 7:44 ` Kip Macy
2005-09-30 16:15 ` Jonathan M. McCune
2005-09-30 16:26 ` Ewan Mellor
2005-09-30 18:03 ` Kip Macy
2005-09-30 20:30 ` Jonathan M. McCune
2005-09-30 20:49 ` Kip Macy
2005-09-30 21:11 ` Jonathan M. McCune [this message]
2005-10-05 15:35 ` Steven Smith
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=433DA9F5.6060609@cmu.edu \
--to=jonmccune@cmu.edu \
--cc=arvinds@cs.cmu.edu \
--cc=kip.macy@gmail.com \
--cc=nahieu@gmail.com \
--cc=parno@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.