Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Janis Johnson <janisjo@codesourcery.com>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Regression: Re: [patch] let gdb.base/reread.exp handle multiple binary files
Date: Sat, 07 May 2011 06:05:00 -0000	[thread overview]
Message-ID: <20110507060431.GA28099@host1.jankratochvil.net> (raw)
In-Reply-To: <4DC2D106.3060806@codesourcery.com>

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

On Thu, 05 May 2011 18:32:06 +0200, Janis Johnson wrote:
> On 05/04/2011 10:55 AM, Pedro Alves wrote:
> > On Wednesday 04 May 2011 17:47:45, Janis Johnson wrote:
> >>         * lib/gdb.exp (exec_target_file, exec_symbol_file,
> >>         gdb_rename_execfile, gdb_touch_execfile): New.
> >>         * gdb.base/reread.exp: Use new procs to handle multiple
> >>         exec files.
> > 
> > Okay.
> 
> Thanks, I got set up with write access and checked it in.

-PASS: gdb.base/reread.exp: run to foo() second time
+FAIL: gdb.base/reread.exp: run to foo() second time
-PASS: gdb.base/reread.exp: second pass: run to foo() second time
+FAIL: gdb.base/reread.exp: second pass: run to foo() second time

52dbcea59b9496cbbdfe0ca30c0308b16e892c0d is the first bad commit
commit 52dbcea59b9496cbbdfe0ca30c0308b16e892c0d
Author: janis <janis>
Date:   Thu May 5 16:29:57 2011 +0000

	* lib/gdb.exp (exec_target_file, exec_symbol_file,
	gdb_rename_execfile, gdb_touch_execfile): New.
	* gdb.base/reread.exp: Use new procs to handle multiple
	exec files.

:040000 040000 21dd778fff93776e04803a94be62e784971e25b9 bde8683b59aaf5806cc96c6a3f8f8ae30a128a2f M      gdb
bisect run success

On {x86_64,x86_64-m32,i686}-fedora{13,14,15,rawhide}-linux-gnu.

It reliably PASSed before, now it FAILs in 90% of cases but occasionally
PASSes, there is some race, I will check it later, it may be machine
dependent.


Thanks,
Jan

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

diff -dup -ru pass/gdb.log fail/gdb.log
--- pass/gdb.log	2011-05-07 07:55:06.000000000 +0200
+++ fail/gdb.log	2011-05-07 07:59:23.000000000 +0200
@@ -1,4 +1,4 @@
-Test Run By jkratoch on Sat May  7 07:55:04 2011
+Test Run By jkratoch on Sat May  7 07:59:22 2011
 Native configuration is x86_64-unknown-linux-gnu
 
 		=== gdb tests ===
@@ -49,19 +49,17 @@ shell sleep 1
 (gdb) run 
 The program being debugged has been started already.
 Start it from the beginning? (y or n) y
-`/home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.base/reread' has changed; re-reading symbols.
 Starting program: /home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.base/reread 
-
-Breakpoint 1, foo () at ./gdb.base/reread2.c:9
-9	  x++;
-(gdb) PASS: gdb.base/reread.exp: run to foo() second time
+This is foo
+[Inferior 1 (process 2994) exited normally]
+(gdb) FAIL: gdb.base/reread.exp: run to foo() second time
 dir
 Reinitialize source path to empty? (y or n) y
 Source directories searched: $cdir:$cwd
 (gdb) dir ./gdb.base
 Source directories searched: /home/jkratoch/redhat/gdb-clean/gdb/testsuite/./gdb.base:$cdir:$cwd
 (gdb) kill
-Kill the program being debugged? (y or n) y
+The program is not being run.
 (gdb) file /home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.base/reread
 Load new symbol table from "/home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.base/reread"? (y or n) y
 Reading symbols from /home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.base/reread...done.
@@ -77,20 +75,19 @@ Breakpoint 1, foo () at ./gdb.base/rerea
 (gdb) PASS: gdb.base/reread.exp: second pass: run to foo()
 continue
 Continuing.
-[Inferior 1 (process 28071) exited normally]
+[Inferior 1 (process 3000) exited normally]
 (gdb) PASS: gdb.base/reread.exp: continue until exit at second pass
 run 
-`/home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.base/reread' has changed; re-reading symbols.
 Starting program: /home/jkratoch/redhat/gdb-clean/gdb/testsuite/gdb.base/reread 
-
-Breakpoint 1, foo () at ./gdb.base/reread2.c:9
-9	  x++;
-(gdb) PASS: gdb.base/reread.exp: second pass: run to foo() second time
-testcase ./gdb.base/reread.exp completed in 2 seconds
+This is foo
+[Inferior 1 (process 3003) exited normally]
+(gdb) FAIL: gdb.base/reread.exp: second pass: run to foo() second time
+testcase ./gdb.base/reread.exp completed in 1 seconds
 
 		=== gdb Summary ===
 
-# of expected passes		7
+# of expected passes		5
+# of unexpected failures	2
 Executing on host: /home/jkratoch/redhat/gdb-clean/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/jkratoch/redhat/gdb-clean/gdb/testsuite/../data-directory --version    (timeout = 300)
 spawn -ignore SIGHUP /home/jkratoch/redhat/gdb-clean/gdb/testsuite/../../gdb/gdb -nw -nx -data-directory /home/jkratoch/redhat/gdb-clean/gdb/testsuite/../data-directory --version
 GNU gdb (GDB) 7.3.50.20110506-cvs
@@ -104,4 +101,4 @@ For bug reporting instructions, please s
 <http://www.gnu.org/software/gdb/bugs/>.
 /home/jkratoch/redhat/gdb-clean/gdb/testsuite/../../gdb/gdb version  7.3.50.20110506-cvs -nw -nx -data-directory /home/jkratoch/redhat/gdb-clean/gdb/testsuite/../data-directory 
 
-runtest completed at Sat May  7 07:55:06 2011
+runtest completed at Sat May  7 07:59:23 2011
diff -dup -ru pass/gdb.sum fail/gdb.sum
--- pass/gdb.sum	2011-05-07 07:55:06.000000000 +0200
+++ fail/gdb.sum	2011-05-07 07:59:23.000000000 +0200
@@ -1,4 +1,4 @@
-Test Run By jkratoch on Sat May  7 07:55:04 2011
+Test Run By jkratoch on Sat May  7 07:59:22 2011
 Native configuration is x86_64-unknown-linux-gnu
 
 		=== gdb tests ===
@@ -10,14 +10,15 @@ Running target unix
 Running ./gdb.base/reread.exp ...
 PASS: gdb.base/reread.exp: breakpoint foo in first file
 PASS: gdb.base/reread.exp: run to foo()
-PASS: gdb.base/reread.exp: run to foo() second time
+FAIL: gdb.base/reread.exp: run to foo() second time
 PASS: gdb.base/reread.exp: second pass: breakpoint foo in first file
 PASS: gdb.base/reread.exp: second pass: run to foo()
 PASS: gdb.base/reread.exp: continue until exit at second pass
-PASS: gdb.base/reread.exp: second pass: run to foo() second time
+FAIL: gdb.base/reread.exp: second pass: run to foo() second time
 
 		=== gdb Summary ===
 
-# of expected passes		7
+# of expected passes		5
+# of unexpected failures	2
 /home/jkratoch/redhat/gdb-clean/gdb/testsuite/../../gdb/gdb version  7.3.50.20110506-cvs -nw -nx -data-directory /home/jkratoch/redhat/gdb-clean/gdb/testsuite/../data-directory 
 

  reply	other threads:[~2011-05-07  6:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 16:47 Janis Johnson
2011-05-04 17:55 ` Pedro Alves
2011-05-05 16:32   ` Janis Johnson
2011-05-07  6:05     ` Jan Kratochvil [this message]
2011-05-08  9:08       ` [patch] Regression: " Jan Kratochvil
2011-05-11  7:08         ` [patch#2] " Jan Kratochvil
2011-05-11  9:03           ` Pedro Alves
2011-05-11  9:12             ` Jan Kratochvil

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=20110507060431.GA28099@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=janisjo@codesourcery.com \
    --cc=pedro@codesourcery.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