From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite] rewrite get_compiler_info
Date: Wed, 07 Jan 2004 02:51:00 -0000 [thread overview]
Message-ID: <20040107025046.GA7615@nevyn.them.org> (raw)
In-Reply-To: <20040107013455.049834B35A@berman.michael-chastain.com>
I have not completely reviewed this patch yet. However,
On Tue, Jan 06, 2004 at 08:34:55PM -0500, Michael Chastain wrote:
> The drawback is that the output of "gcc -E ..." winds up in gdb.log.
> Twice. (dejagnu turns on output logging, and then sends copies of the
> captured output to the log also). I fixed that by toggling the log
> file at the expect level.
Is it possible to do this in gdb_compile instead? If you check
gdb.log, currently compiler error messages get logged twice. Sounds
like the same problem.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-07 2:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 1:34 Michael Elizabeth Chastain
2004-01-07 2:51 ` Daniel Jacobowitz [this message]
2004-01-07 3:16 Michael Elizabeth Chastain
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=20040107025046.GA7615@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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