From: Keith Seitz <kseitz@uglyboxes.com>
To: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: [RFA] breakpoints/13798 and mi/11541 (tests only)
Date: Wed, 13 Jun 2012 17:54:00 -0000 [thread overview]
Message-ID: <4FD8D3C2.4090001@uglyboxes.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
Hi,
Both of the bugs involve filenames with spaces and colons. The linespec
parser rewrite fixed these bugs, and while there were a few tests that
dealt with these cases already, I'd like to add a couple more just to
cover some additional bases.
Ok?
testsuite/ChangeLog
2012-06-13 Keith Seitz <keiths@redhat.com>
PR breakpoints/13798 and mi/11541
* gdb.linespec/ls-errs.exp: Add a few more tests for
filenames with spaces and colons.
[-- Attachment #2: 11541-13798.patch --]
[-- Type: text/x-patch, Size: 847 bytes --]
Index: testsuite/gdb.linespec/ls-errs.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.linespec/ls-errs.exp,v
retrieving revision 1.1
diff -u -p -r1.1 ls-errs.exp
--- testsuite/gdb.linespec/ls-errs.exp 5 Apr 2012 18:50:29 -0000 1.1
+++ testsuite/gdb.linespec/ls-errs.exp 13 Jun 2012 17:53:14 -0000
@@ -116,7 +116,9 @@ foreach x [list "this_file_doesn't_exist
"\"this \"file\" has quotes.c\"" \
"'this \"file\" has quotes.c'" \
"'this 'file' has quotes.c'" \
- "\"this 'file' has quotes.c\""] {
+ "\"this 'file' has quotes.c\"" \
+ "\"spaces: and :colons.c\"" \
+ "'more: :spaces: :and colons::.c'"] {
# Remove any quoting from FILENAME for the error message.
add the_tests "$x:3" invalid_file [string trim $x \"']
}
next reply other threads:[~2012-06-13 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 17:54 Keith Seitz [this message]
2012-06-13 18:00 ` Tom Tromey
2012-06-13 18:12 ` Keith Seitz
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=4FD8D3C2.4090001@uglyboxes.com \
--to=kseitz@uglyboxes.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