Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Joe Knowling <linux_joe2003@yahoo.com>
Cc: gdb@sources.redhat.com
Subject: Re: getting gdb output redirected to a file
Date: Thu, 14 Nov 2002 10:21:00 -0000	[thread overview]
Message-ID: <20021114182241.GA30103@nevyn.them.org> (raw)
In-Reply-To: <20021114181655.19356.qmail@web9301.mail.yahoo.com>

On Thu, Nov 14, 2002 at 10:16:55AM -0800, Joe Knowling wrote:
> Hi 
> Ive got a rather basic question. Is there a command
> analogous to fprintf in C to dump output to a file.
> Eg. 
> after starting gdb and attaching to a process I say
> 
> source xyz
> 
> where xyz is a file containing a list of commands for
> gdb to execute. Now instead of doing printf's and
> seeing the data in the gdb window is there an
> alternative like fprintf that can dump output to a
> while
> 
> any help would be appreciated

Not yet.  I submitted some patches for this but they got stalled.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2002-11-14 18:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-14 10:17 Joe Knowling
2002-11-14 10:21 ` Daniel Jacobowitz [this message]

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=20021114182241.GA30103@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=linux_joe2003@yahoo.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