Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Harald Fernengel <harald@trolltech.com>
Cc: gdb@sources.redhat.com
Subject: Re: Need help with GDB commands
Date: Tue, 03 Jul 2001 23:51:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1010704095214.3231K-100000@is> (raw)
In-Reply-To: <20010703185922Z114582-2795+260@trolltech.com>

On Tue, 3 Jul 2001, Harald Fernengel wrote:

> I need to create a user-defined command that reads some memory and then
> passes it a formatting program.  I am assuming the formatting program would
> be run via the 'shell' command'.  Is there any way to do this?
> 
> Below is a list of the things that I have thought of.  None of them seem to
> be possible:
> 
> * Writing the command output to a file (this is my preferred approach)
> * Passing output as stdin to a child process
> * Setting an environment variable which contains the output
> * Passing output as command line parameters to a child process

I'd suggest

 * add a special function to the debuggee which will accept the
   command line for the formatting program, and then run that
   program.  Then use the GDB `call' command to invoke that function
   from GDB.

> Another possible solution would be to call C runtime I/O functions as part
> an expression in a 'set' command.  However, these functions would be
> running on the target, not the gdb host machine right?

Ah, you are debugging a remote target?  Than my suggestion won't work
for you.

Sounds like a good reason for extending `shell', or maybe for a new
command.


  reply	other threads:[~2001-07-03 23:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-03 12:01 Harald Fernengel
2001-07-03 23:51 ` Eli Zaretskii [this message]
2001-07-03 23:56   ` Eli Zaretskii

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=Pine.SUN.3.91.1010704095214.3231K-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=gdb@sources.redhat.com \
    --cc=harald@trolltech.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