Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: dje@google.com
Cc: gdb-patches@sourceware.org
Subject: Regression for gdb.base/stap-probe.exp (and some others)  [Re: [patch] Have gdb_breakpoint call pass]
Date: Fri, 12 Oct 2012 07:02:00 -0000	[thread overview]
Message-ID: <20121012070149.GA5873@host2.jankratochvil.net> (raw)
In-Reply-To: <yjt2y5jqb0j2.fsf@ruffy2.mtv.corp.google.com>

On Mon, 01 Oct 2012 18:49:21 +0200, dje@google.com wrote:
> 2012-10-01  Doug Evans  <dje@google.com>
> 
> 	* lib/gdb.exp (gdb_breakpoint): Fix varargs scan.
> 	Recognize "message" -> print pass and fail.  Add eof case.
> 	(runto): Recognize message, no-message.  Print pass/fail if requested,
> 	with same treatment as gdb_breakpoint.
> 	(runto_main): Pass no-message to runto.
> 	(gdb_internal_error_resync): Add log message.
> 	(gdb_file_cmd): Tweak internal error fail text for consistency.

 Running gdb/testsuite/gdb.base/stap-probe.exp ...
 PASS: gdb.base/stap-probe.exp: without semaphore, not optimized: check argument not at probe point
 PASS: gdb.base/stap-probe.exp: without semaphore, not optimized: info probes stap
-PASS: gdb.base/stap-probe.exp: without semaphore, not optimized: run to -pstap test:user
+FAIL: gdb.base/stap-probe.exp: without semaphore, not optimized: run to -pstap test:user
[...]
(many of PASS->FAIL for gdb.base/stap-probe.exp)

8ff7e49469b5392bd0663a503023b9987dd1b9de is the first bad commit
commit 8ff7e49469b5392bd0663a503023b9987dd1b9de
Author: Doug Evans <dje@google.com>
Date:   Thu Oct 11 15:59:56 2012 +0000

	* lib/gdb.exp (gdb_breakpoint): Fix varargs scan.
	Recognize "message" -> print pass and fail.  Add eof case.
	(runto): Recognize message, no-message.  Print pass/fail if requested,
	with same treatment as gdb_breakpoint.
	(runto_main): Pass no-message to runto.
	(gdb_internal_error_resync): Add log message.
	(gdb_file_cmd): Tweak internal error fail text for consistency.


-(gdb) break -pstap test:user
-Breakpoint 2 at 0x4005a1
-(gdb) run 
-[...]
-(gdb) PASS: gdb.base/stap-probe.exp: without semaphore, not optimized: run to -pstap test:user
+(gdb) break -pstap
+Function "-pstap" not defined.
+Make breakpoint pending on future shared library load? (y or [n]) n
+(gdb) FAIL: gdb.base/stap-probe.exp: without semaphore, not optimized: run to -pstap test:user


Also:
 (gdb) break jmisc.main(java.lang.String[])
 Function "jmisc.main(java.lang.String[])" not defined.
-Make breakpoint pending on future shared library load? (y or [n]) y
-Breakpoint 2 (jmisc.main(java.lang.String[])) pending.
[...]
+Make breakpoint pending on future shared library load? (y or [n]) n
+(gdb) FAIL: gdb.java/jmisc.exp: setting breakpoint at jmisc.main(java.lang.String[])



Regards,
Jan


  reply	other threads:[~2012-10-12  7:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01 16:49 [patch] Have gdb_breakpoint call pass dje
2012-10-12  7:02 ` Jan Kratochvil [this message]
2012-10-15 13:50   ` Regression for gdb.base/stap-probe.exp (and some others) [Re: [patch] Have gdb_breakpoint call pass] Doug Evans
2012-10-15 17:41   ` dje
2012-10-15 18:35     ` Jan Kratochvil
2012-10-15 18:50       ` Doug Evans
2012-10-15 19:12         ` [commit] " 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=20121012070149.GA5873@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=dje@google.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