Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: Sheng-Liang Song <ssl@baymicrosystems.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	 gdb@sourceware.org, 	  jan.kratochvil@redhat.com,
	 koling@kchang.net
Subject: Re: reference environment variables from gdb scripts  (gdb and unix  pipe)
Date: Tue, 28 Aug 2007 21:03:00 -0000	[thread overview]
Message-ID: <m3d4x7pe21.fsf@codesourcery.com> (raw)
In-Reply-To: <46D31638.5030200@baymicrosystems.com> (Sheng-Liang Song's message of "Mon, 27 Aug 2007 11:21:44 -0700")


Sheng-Liang Song <ssl@baymicrosystems.com> writes:
> gdb has "shell" command to switch to a unix shell.
> After switch to a unix shell, can I call gdb functions/commands?

No; you need to exit the shell before you can give more commands to
GDB.

> Does gdb supports "pipe" command? Is there a plan to add a "unix pipe"
> command to gdb debug prompt?

No; we don't have any plans to do so.

We're currently planning to add Python as a scripting language to
GDB.  If that were to happen, the things you mention here could be
done in a clean and general way.


  reply	other threads:[~2007-08-28 21:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-23 21:19 reference environment variables from gdb scripts rockwellkc
2007-08-24  8:58 ` Jan Kratochvil
2007-08-24 16:38   ` Sheng-Liang Song
2007-08-24 17:30     ` Eli Zaretskii
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 [this message]
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=m3d4x7pe21.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=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