From: Yao Qi <yao@codesourcery.com>
To: "catalin.udma@freescale.com" <catalin.udma@freescale.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Cc: Adrian Sendroiu <adrian.sendroiu@freescale.com>
Subject: Re: qSymbol when using symbol-file
Date: Wed, 18 Jun 2014 02:27:00 -0000 [thread overview]
Message-ID: <53A0F88F.3020004@codesourcery.com> (raw)
In-Reply-To: <ceacc600bb1d4e4891e074158fb1cd50@BY2PR03MB175.namprd03.prod.outlook.com>
On 06/03/2014 04:58 PM, catalin.udma@freescale.com wrote:
> In the gdb/gdbserver scenario, gdb is not sending qSymbol packet when using "symbol-file", without "file" or "exec-file".
> The steps are:
> start gdb (with no arguments)
> (gdb) symbol-file <file>
> (gdb) target remote <ip>:<port>
> -> qSymbol packet is not sent.
I can reproduce it on GDB 7.7, but can't reproduce it on GDB HEAD
(20140617) and 7.8 pre-release (gdb-7.7.90).
1. Start gdbserver
$ ./gdbserver/gdbserver :1234 ./testsuite/gdb.base/wchar
2. Start gdb
$ ./gdb
(gdb) symbol-file ./testsuite/gdb.base/wchar
Reading symbols from ./testsuite/gdb.base/wchar...done.
(gdb) set debug remote 1
(gdb) target remote :1234
....
0x42d0c050 in ?? ()
Sending packet: $qSymbol::#5b...Packet received:
qSymbol:6764625f6167656e745f6764625f74705f686561705f627566666572
Packet qSymbol (symbol-lookup) is supported
Sending packet:
$qSymbol::6764625f6167656e745f6764625f74705f686561705f627566666572#1e...Packet
received: qSymbol:6e70746c5f76657273696f6e
Sending packet: $qSymbol::6e70746c5f76657273696f6e#4d...Packet received: OK
qSymbol is sent. You can use gdb 7.8 which will be released soon.
--
Yao (é½å°§)
next prev parent reply other threads:[~2014-06-18 2:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 8:59 catalin.udma
2014-06-16 6:58 ` catalin.udma
2014-06-18 2:27 ` Yao Qi [this message]
2014-06-18 13:43 ` Tim Sander
2014-06-18 14:00 ` Yao Qi
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=53A0F88F.3020004@codesourcery.com \
--to=yao@codesourcery.com \
--cc=adrian.sendroiu@freescale.com \
--cc=catalin.udma@freescale.com \
--cc=gdb@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