public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v6 7/9] Explicit locations: add UI features for CLI
Date: Mon, 17 Aug 2015 16:41:00 -0000	[thread overview]
Message-ID: <86a8tp50le.fsf@gmail.com> (raw)
In-Reply-To: <1439325928-4723-1-git-send-email-keiths@redhat.com> (Keith	Seitz's message of "Tue, 11 Aug 2015 13:45:28 -0700")

Keith Seitz <keiths@redhat.com> writes:

Hi Keith,

> +    set tst "complete unique function name"
> +    send_gdb "break -function mai\t"
> +    gdb_test_multiple "" $tst {
> +	"break -function mai\\\x07n" {
> +	    send_gdb "\n"
> +	    gdb_test "" ".*Breakpoint \[0-9\]+.*" $tst
> +	    gdb_test_no_output "delete \$bpnum" "delete $tst breakpoint"
> +	}
> +    }

I got some timeout FAILs on my ubuntu x86_64 machine.

(gdb) PASS: gdb.linespec/explicit.exp: complete -line with no value
break -function main FAIL: gdb.linespec/explicit.exp: complete unique function name (timeout)
break -function myfunc^H^H^H^H^Hain ^[[KFAIL: gdb.linespec/explicit.exp: complete non-unique function name (timeout)
break -function foo^H^H^Hmain FAIL: gdb.linespec/explicit.exp: complete non-existant function name (timeout)
break -source 3ex^G^H^H^H/home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.linespec/FAIL: gdb.linespec/explicit.exp: complete unique file name (timeout)
break -source exp^G^H^H^H/home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.linespec/FAIL: gdb.linespec/explicit.exp: complete non-unique file name (timeout)
break -source foo^G^H^H^H/home/yao/SourceCode/gnu/gdb/git/gdb/testsuite/gdb.linespec/ERROR: Process no longer exists
UNRESOLVED: gdb.linespec/explicit.exp: complete non-existant file name

The fails are shown on Debian-s390x too,
https://www.sourceware.org/ml/gdb-testers/2015-q3/msg06879.html I
haven't look into them yet.

-- 
Yao (齐尧)

  parent reply	other threads:[~2015-08-17 16:41 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05 23:28 [PATCH v6 0/9] Series short description Keith Seitz
2015-08-05 23:29 ` [PATCH v6 1/9] Explicit locations: rename "address string"/"addr_string" to "location" Keith Seitz
2015-08-10 16:43   ` Doug Evans
2015-08-05 23:29 ` [PATCH v6 3/9] Explicit locations: use new location API Keith Seitz
2015-08-10 18:02   ` Doug Evans
2015-08-05 23:29 ` [PATCH v6 2/9] Explicit locations: introduce new struct event_location-based API Keith Seitz
2015-08-10 17:34   ` Doug Evans
2015-08-10 18:05     ` Keith Seitz
2015-08-10 19:59       ` Doug Evans
2015-08-11 20:45         ` [PATCH v6 2/9] Explicit locations: introduce new struct event_locations-based API Keith Seitz
2015-08-11 21:49           ` Doug Evans
2015-08-05 23:30 ` [PATCH v6 5/9] Explicit locations: introduce probe locations Keith Seitz
2015-08-10 18:06   ` Doug Evans
2015-08-05 23:30 ` [PATCH v6 4/9] Explicit locations: introduce address locations Keith Seitz
2015-08-10 18:04   ` Doug Evans
2015-12-14  7:11   ` Joel Brobecker
2015-12-14 20:56     ` Keith Seitz
2015-12-15 13:40       ` Joel Brobecker
2016-01-17 15:32         ` [RFA] Fix regression introduced in "break *<EXPR>" by explicit location patches (was: "Re: [PATCH v6 4/9] Explicit locations: introduce address locations") Joel Brobecker
2016-01-18 21:29           ` [RFA] Fix regression introduced in "break *<EXPR>" by explicit location patches Keith Seitz
2016-01-21 10:33             ` Joel Brobecker
2015-08-05 23:32 ` [PATCH v6 6/9] Explicit locations: introduce explicit locations Keith Seitz
2015-08-10 18:09   ` Doug Evans
2015-08-05 23:33 ` [PATCH v6 8/9] Explicit locations: MI support for " Keith Seitz
2015-08-10 19:43   ` Doug Evans
2015-08-05 23:33 ` [PATCH v6 7/9] Explicit locations: add UI features for CLI Keith Seitz
2015-08-10 19:42   ` Doug Evans
2015-08-11 20:45     ` Keith Seitz
2015-08-11 21:50       ` Doug Evans
2015-08-17 16:41       ` Yao Qi [this message]
2015-08-17 17:19         ` Keith Seitz
2015-08-05 23:34 ` [PATCH v6 9/9] Explicit locations: documentation updates Keith Seitz
2015-08-10 19:45   ` Doug Evans
2015-08-10 19:54 ` [PATCH v6 0/9] Series short description Doug Evans

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=86a8tp50le.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).