From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15588 invoked by alias); 25 Nov 2002 06:24:33 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 15576 invoked from network); 25 Nov 2002 06:24:31 -0000 Received: from unknown (HELO is.elta.co.il) (199.203.121.2) by sources.redhat.com with SMTP; 25 Nov 2002 06:24:31 -0000 Received: from is (is [199.203.121.2]) by is.elta.co.il (8.9.3/8.8.8) with SMTP id IAA10369; Mon, 25 Nov 2002 08:24:20 +0200 (IST) Date: Sun, 24 Nov 2002 22:24:00 -0000 From: Eli Zaretskii X-Sender: eliz@is To: Per Fransson cc: gdb mailing list Subject: Re: redirecting output In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-11/txt/msg00349.txt.bz2 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.