From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Regression for gdb.base/stap-probe.exp (and some others) [Re: [patch] Have gdb_breakpoint call pass]
Date: Mon, 15 Oct 2012 13:50:00 -0000 [thread overview]
Message-ID: <CADPb22Ta1pM3-Xe9iPw=oFKO-OF-F2vAuaEUphfiYy++g0LUWA@mail.gmail.com> (raw)
In-Reply-To: <20121012070149.GA5873@host2.jankratochvil.net>
On Fri, Oct 12, 2012 at 12:01 AM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> 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
Sorry about that.
I have a fix I hope to be able to install today.
next prev parent reply other threads:[~2012-10-15 13:50 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 ` Regression for gdb.base/stap-probe.exp (and some others) [Re: [patch] Have gdb_breakpoint call pass] Jan Kratochvil
2012-10-15 13:50 ` Doug Evans [this message]
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='CADPb22Ta1pM3-Xe9iPw=oFKO-OF-F2vAuaEUphfiYy++g0LUWA@mail.gmail.com' \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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