From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26653 invoked by alias); 7 Jan 2004 03:16:09 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 26646 invoked from network); 7 Jan 2004 03:16:08 -0000 Received: from unknown (HELO smtp10.atl.mindspring.net) (207.69.200.246) by sources.redhat.com with SMTP; 7 Jan 2004 03:16:08 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by smtp10.atl.mindspring.net with esmtp (Exim 3.33 #1) id 1Ae4AU-0005wJ-00; Tue, 06 Jan 2004 22:15:38 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 6C35A4B35A; Tue, 6 Jan 2004 22:16:00 -0500 (EST) To: drow@mvista.com, mec.gnu@mindspring.com Subject: Re: [rfa/testsuite] rewrite get_compiler_info Cc: gdb-patches@sources.redhat.com Message-Id: <20040107031600.6C35A4B35A@berman.michael-chastain.com> Date: Wed, 07 Jan 2004 03:16:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-01/txt/msg00157.txt.bz2 drow> Is it possible to do this in gdb_compile instead? Well, as far as the "instead" part goes, I don't want any copies of "gcc -E compiler.c" in the log at all. So I have to disable the logging that happens in dejagnu as well as the logging that happens in gdb_compile. drow> If you check gdb.log, currently compiler error messages get logged drow> twice. Sounds like the same problem. Error messages appear THREE times in gdb.log. I'm vague about the difference between stdout and stderr here but that doesn't matter at this stage. When the compiler produces error messages: (1) In dejagnu, runtest.exp sets up "expect" logging with the call: log_file -a "$outdir/$tool.log". That puts one copy in gdb.log. (2) In dejagnu, default_target_compile calls "verbose -log ...". That puts a second copy in gdb.log. (3) In gdb, gdb_compile says: "clone_output ...". That puts a third copy in gdb.log. It also puts one copy in gdb.sum and one copy on the standard output or standard_error (I'm capturing them both in a single file anyways). So in dejagnu, default_target_compile should call "verbose ..." instead of "verbose -log ...". Or maybe just STFU. And in gdb, gdb_compile should not use "clone_output". gdb_compile could do something that writes to stdout/stderr and writes to gdb.sum but does not write to gdb.log. Off hand, I don't know how to do that. Or we could just make gdb_compile more quiet as well. Like, have it raise some kind of test result, but not print any messages to stdout/stderr or gdb.sum. Michael C