From: "catalin.udma@freescale.com" <catalin.udma@freescale.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Cc: Adrian Sendroiu <adrian.sendroiu@freescale.com>
Subject: qSymbol when using symbol-file
Date: Tue, 03 Jun 2014 08:59:00 -0000 [thread overview]
Message-ID: <ceacc600bb1d4e4891e074158fb1cd50@BY2PR03MB175.namprd03.prod.outlook.com> (raw)
Hi,
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.
If the "file" command is used instead of "symbol-file", the qSymbol packet is sent to gdbserver.
The question makes more sense in the following context: Using Eclipse and DSF -GDB Hardware Debugging . Here, Eclipse is not using "file", but only "symbol-file" ( as explained why here: [1] ). This makes qSymbol notification not working.
My questions/comments:
- In the above scenario, does make sense to enable qSymbol notification even when the exec-file is not specified? Here is not required to specify the exec file. Or even in the gdb/gdbserver scenario where the application/executable is started by gdbserver on target.
- For the particular case when some symbol files are added after "target remote", gdb is sending qSymbol, even without having the exec file specified. The above proposal would be in sync with this.
- What would be your other thoughts to fix the qSymbol for the gdb + Eclipse with DSF GDB Hardware Debugging scenario ?
Regards,
Catalin
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=310304
next reply other threads:[~2014-06-03 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 8:59 catalin.udma [this message]
2014-06-16 6:58 ` catalin.udma
2014-06-18 2:27 ` Yao Qi
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=ceacc600bb1d4e4891e074158fb1cd50@BY2PR03MB175.namprd03.prod.outlook.com \
--to=catalin.udma@freescale.com \
--cc=adrian.sendroiu@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