From: Eli Zaretskii <eliz@is.elta.co.il>
To: Per Fransson <fransson@cs.lth.se>
Cc: gdb mailing list <gdb@sources.redhat.com>
Subject: Re: redirecting output
Date: Sun, 24 Nov 2002 22:24:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1021125082311.9888F-100000@is> (raw)
In-Reply-To: <Pine.GSO.4.33.0211250108110.12739-100000@ygg>
On Mon, 25 Nov 2002, Per Fransson wrote:
> % gdb a.out --command=command_file > pc_log
>
>
> Unfortunately it doesn't seem to work. Somehow the execution gets
> corrupted. The 'pc_log' file deviates from what I get by just letting gdb
> print to stdout like this (they come to different concusions at some
> conditional branch):
>
> % gdb a.out --command=command_file
>
>
> I find this very puzzling. Can someone tell me what's going on? And,
> better yet, how I can get the pc log I'm looking for?
The best technique as of now is to use the `script' command (assuming you
are on a Posix host) or some work-alike.
Adding a feature you would like to have is a long-standing TODO item in
GDB development.
next prev parent reply other threads:[~2002-11-25 6:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-24 16:29 Per Fransson
2002-11-24 22:24 ` Eli Zaretskii [this message]
2002-11-27 13:25 ` Ben Elliston
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.1021125082311.9888F-100000@is \
--to=eliz@is.elta.co.il \
--cc=fransson@cs.lth.se \
--cc=gdb@sources.redhat.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