From: Eli Zaretskii <eliz@gnu.org>
To: Sheng-Liang Song <ssl@baymicrosystems.com>
Cc: jan.kratochvil@redhat.com, koling@kchang.net, gdb@sourceware.org
Subject: Re: reference environment variables from gdb scripts
Date: Fri, 24 Aug 2007 17:30:00 -0000 [thread overview]
Message-ID: <ur6lsvo1c.fsf@gnu.org> (raw)
In-Reply-To: <46CF0945.8090901@baymicrosystems.com> (message from Sheng-Liang Song on Fri, 24 Aug 2007 09:37:25 -0700)
> Date: Fri, 24 Aug 2007 09:37:25 -0700
> From: Sheng-Liang Song <ssl@baymicrosystems.com>
>
> BTW, Is there a gdb script functional document?
The GDB scripting commands are documented in the GDB user manual. See
the node "Sequences".
next prev parent reply other threads:[~2007-08-24 17:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 21:19 rockwellkc
2007-08-24 8:58 ` Jan Kratochvil
2007-08-24 16:38 ` Sheng-Liang Song
2007-08-24 17:30 ` Eli Zaretskii [this message]
2007-08-24 18:29 ` Sheng-Liang Song
2007-08-25 9:58 ` Eli Zaretskii
2007-08-27 18:30 ` reference environment variables from gdb scripts (gdb and unix pipe) Sheng-Liang Song
2007-08-28 21:03 ` Jim Blandy
2007-08-28 21:08 ` GDB Tool Chains McGuerty, Jay S.
2007-08-28 21:56 ` Peter Toft
2007-08-28 21:59 ` Jim Blandy
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=ur6lsvo1c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=koling@kchang.net \
--cc=ssl@baymicrosystems.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