From: "Xinan Tang" <xinan@TidalNetworks.net>
To: "Monika Chaddha" <monika@acmet.com>
Cc: <gdb@sources.redhat.com>
Subject: RE: "Show command execution list"
Date: Thu, 23 Sep 2004 16:44:00 -0000 [thread overview]
Message-ID: <52BBA75459915749B68F93B604B636CD0666F1@neptune.TidalNetworks.net> (raw)
Hi Monika,
Thanks for your reply. That is exactly what I have been doing right
for the moment. I wonder whether there is a better solution.
Thanks
--Xinan
-----Original Message-----
From: Monika Chaddha [mailto:monika@acmet.com]
Sent: Thursday, September 23, 2004 12:46 AM
To: Xinan Tang
Cc: acmet@vsnl.net; gdb@sources.redhat.com
Subject: RE: "Show command execution list"
I can suggest one temporary method:-
Suppose there is a command to be execute in command script file as
"target exec $arg0"
Now we want to execute it as well as want to see this command on console
Than put one echo command just before this in the following manner for
the above command
"echo target exec $arg0"
Now the command to be executed will print first on the console and than
it will execute. The commands given to GDB from a script file can be
seen on the console.
Will this trick help?
Regards
Monika
>-----Original Message-----
>From: gdb-owner@sources.redhat.com
[mailto:gdb-owner@sources.redhat.com] On
>Behalf Of Xinan Tang
>Sent: Thursday, September 23, 2004 8:27 AM
>To: gdb@sources.redhat.com
>Subject: "Show command execution list"
>
>Hi
>
> When starting GDB with '-x command-file', the list of commands being
>executed will not be shown anymore. Is it possible to display those
>commands on the screen?
>
> What I want is to show those commands on the screen not on a log
file.
>
>Thanks
>
>--Xinan
next reply other threads:[~2004-09-23 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 16:44 Xinan Tang [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-23 2:58 Xinan Tang
2004-09-23 12:26 ` Monika Chaddha
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=52BBA75459915749B68F93B604B636CD0666F1@neptune.TidalNetworks.net \
--to=xinan@tidalnetworks.net \
--cc=gdb@sources.redhat.com \
--cc=monika@acmet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox