From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: GDB Development <gdb@sourceware.org>
Subject: Re: RFC - changes to the test suite
Date: Tue, 26 Feb 2013 19:00:00 -0000 [thread overview]
Message-ID: <87621e3nox.fsf@fleche.redhat.com> (raw)
In-Reply-To: <51231E07.3010100@codesourcery.com> (Yao Qi's message of "Tue, 19 Feb 2013 14:39:03 +0800")
Tom> So, the first question is -- does anybody care strongly about where the
Tom> files end up? And, if you do care, why do you care?
Yao> When running testsuite with boardfile native-gdbserver.exp, does
Yao> GDBserver need to know the updated location of files? or do we plan to
Yao> spawn GDBserver in "./outputs/gdb.DIR/FILE" directory?
I will test it and find out.
Tom> I also added an "inotify" mode to the tests so you can easily see which
Tom> tests write files outside of their specified directory. There are still
Tom> a few remaining, I ran out of steam dotting every "i".
Yao> What is the motivation of adding "inotify" mode? to monitor the
Yao> progress of a given test, or something else?
It is just for debugging the code to ensure that tests don't write
outside of the allowed directories. It isn't perfect, but it helped me
find some bugs, and I thought it would be handy to keep around.
Tom
prev parent reply other threads:[~2013-02-26 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 17:57 Tom Tromey
2013-02-18 19:20 ` Joel Brobecker
2013-02-18 19:40 ` Jan Kratochvil
2013-02-18 20:46 ` Tom Tromey
2013-02-19 5:10 ` Jan Kratochvil
2013-02-19 6:40 ` Yao Qi
2013-02-26 19:00 ` Tom Tromey [this message]
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=87621e3nox.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=yao@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