This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 2/4] introduce parallel mode
- From: Tom Tromey <tromey at redhat dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: <gdb-patches at sourceware dot org>
- Date: Thu, 01 Aug 2013 13:44:53 -0600
- Subject: Re: [PATCH 2/4] introduce parallel mode
- References: <1374073124-23602-1-git-send-email-tromey at redhat dot com> <1374073124-23602-3-git-send-email-tromey at redhat dot com> <51E7E27E dot 5030800 at codesourcery dot com> <87txjsc7mw dot fsf at fleche dot redhat dot com> <51E86A71 dot 3000301 at codesourcery dot com>
>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:
Yao> Probably, we can send the output to the log, for example
Yao> inotify_[pid].log, and check whether there is something written into
Yao> the log in the test somewhere. If there is, emit a FAIL, which would
Yao> be more attractive, like:
I am not sure about emitting a FAIL. There won't be a corresponding
PASS. It would be more noticeable, which is a plus; but in the absence
of a conflict it isn't clearly a FAIL-worthy bug -- even after my series
we'll have a few of these.
So for now I am just teeing the output to the log file:
set inotify_pid [exec inotifywait -r -m -e move,create,delete . \
--exclude $exclusion_re \
|& tee -a $outdir/$tool.log &]
This way it will show up in on the terminal but also in the log.
I'm open to discussion about your idea though. I'm really not sure.
Tom