From: Triple Yang <triple.yang@gmail.com>
To: gdb@sourceware.org
Subject: command-list does not work in my gdb 7.2 port
Date: Mon, 26 Sep 2011 14:58:00 -0000 [thread overview]
Message-ID: <CAGxstLTUF7-G8Hx=_d+wYrnd_kKnLLRdY04mCVGfO88Sc9bSKw@mail.gmail.com> (raw)
Hi, everyone.
I am making a gdb 7.2 port recently for a prototype architecture,
which is a remote debug target in my case. The port is almost done to
achieve my purposes, say:
1. Connecting to remote target and loading program image work well.
2. Control on the debugged program is OK.
3. Inserting/deleting breakpoints OK.
4. and so as some other basic facilities.
But when I tried using gdb command "commands" to specify a command
list after I set a breakpoint, I found this did not work at all. Here
follows a rough example:
(gdb) break main
(gdb) commands
>shell echo test-commands
>end
(gdb) run
In this example, the command list is composed of only one command
"shell echo test-commands". "test-commands" is expected to be output
when the breakpoint is hit, but it does not happen. I tried replacing
"shell echo test-commands" with other similar commands, it still did
not work. but "shell echo" does work well when it is not used in a
command list defined by "commands".
I am not able to find any clue for this situation. Still worse, I can
not provide sufficient information to gdb experts for analysis.
I am hoping that someone who has ever met this problem before can help
me with his/her invaluable suggestions.
Thank you and best regards.
--
Yang Yong-Yong
next reply other threads:[~2011-09-26 14:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 14:58 Triple Yang [this message]
2011-09-27 6:19 ` Hui Zhu
2011-09-27 7:07 ` Triple Yang
2011-09-30 18:15 ` Liang Cheng
2011-10-01 5:34 ` Triple Yang
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='CAGxstLTUF7-G8Hx=_d+wYrnd_kKnLLRdY04mCVGfO88Sc9bSKw@mail.gmail.com' \
--to=triple.yang@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).