Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH] Fix `testrun.log' output of manual `testrun's
Date: Sat, 13 Jan 2007 09:08:00 -0000	[thread overview]
Message-ID: <20070113090837.GA25646@host0.dyn.jankratochvil.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 228 bytes --]

Hi,

if you run by hand:
	cd gdb/testsuite; runtest gdb.base/complex.exp 
	(any test using get_compiler_info())

"testrun.log" will get empty (except its header).

This problem does not occur during `make check'.


Regards,
Jan

[-- Attachment #2: gdb-6.5-testsuite-log.patch --]
[-- Type: text/plain, Size: 787 bytes --]

2007-01-13  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* lib/gdb.exp (get_compiler_info): Cope with nondefault output logs.


diff -u -rupN gdb-6.5-ppc/gdb/testsuite/lib/gdb.exp gdb-6.5/gdb/testsuite/lib/gdb.exp
--- gdb-6.5-ppc/gdb/testsuite/lib/gdb.exp	2007-01-12 14:33:26.000000000 -0500
+++ gdb-6.5/gdb/testsuite/lib/gdb.exp	2007-01-12 21:15:02.000000000 -0500
@@ -1351,9 +1351,10 @@ proc get_compiler_info {binfile args} {
 
     # Run $ifile through the right preprocessor.
     # Toggle gdb.log to keep the compiler output out of the log.
+    set log_old [log_file -info]
     log_file
     set cppout [ gdb_compile "${ifile}" "" preprocess [list "$args" quiet] ]
-    log_file -a "$outdir/$tool.log" 
+    eval "log_file $log_old"
 
     # Eval the output.
     set unknown 0

             reply	other threads:[~2007-01-13  9:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-13  9:08 Jan Kratochvil [this message]
2007-01-13 13:47 ` Mark Kettenis
2007-01-13 16:01 ` Daniel Jacobowitz
2007-01-14 15:34   ` Jan Kratochvil
2007-01-20 19:59     ` Daniel Jacobowitz
2007-01-21 22:28       ` Jan Kratochvil
2007-01-21 22:51         ` Daniel Jacobowitz

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=20070113090837.GA25646@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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