From: "H.J. Lu" <hjl.tools@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, GDB <gdb-patches@sourceware.org>
Subject: Re: How to load XML target description?
Date: Thu, 04 Feb 2010 21:09:00 -0000 [thread overview]
Message-ID: <6dc9ffc81002041309u7d58f4fcj8032f67c89b24a83@mail.gmail.com> (raw)
In-Reply-To: <6dc9ffc81002041306u18ce24bapaa101db921302da8@mail.gmail.com>
On Thu, Feb 4, 2010 at 1:06 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Thu, Feb 4, 2010 at 12:47 PM, Daniel Jacobowitz <dan@codesourcery.com> wrote:
>> On Thu, Feb 04, 2010 at 12:36:35PM -0800, H.J. Lu wrote:
>>> and in gdb I got
>>>
>>> (gdb) target remote :10000
>>> Remote debugging using :10000
>>> warning: while parsing target description (at line 14): Could not load
>>> XML document "32bit-core.xml"
>>> warning: Could not load XML target description; ignoring
>>> Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done.
>>> Loaded symbols for /lib/ld-linux.so.2
>>> 0x0042e850 in _start () from /lib/ld-linux.so.2
>>> (gdb) help set
>>>
>>> 32bit-core.xml is in my gdb source tree and not installed by "make install". How
>>> do I resolve this?
>>
>> See srv_xmlfiles in gdbserver/configure.srv. GDB expects to get the
>> file over the remote protocol.
>>
>
> I set srv_xmlfiles in gdbserver/configure.srv and I saw gdbserve get
>
> handling possible serial event
> getpkt ("qXfer:features:read:32bit-core.xml:0,fff"); [no ack sent]
> putpkt ("$E00#a5"); [noack mode]
>
> For some reason, it wouldn't read the file and send it to gdb. Any suggestions?
>
> Thanks.
I see what is wrong.
--
H.J.
prev parent reply other threads:[~2010-02-04 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 20:36 H.J. Lu
2010-02-04 20:47 ` Daniel Jacobowitz
2010-02-04 21:06 ` H.J. Lu
2010-02-04 21:09 ` H.J. Lu [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=6dc9ffc81002041309u7d58f4fcj8032f67c89b24a83@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox