Christopher Faylor quipped: > It seems pretty clear to me that if this is a really serious problem > for you then the best way to get it fixed is to gain more than zero > knowledge of cygwin.
Gee, thanks. Very helpful. Can you at least type the commands in and verify the problem for me before you get snippy? I said "zero knowlege" in an attempt to be modest*, but if you really want to get into a tussle about developer credentials, I'm happy to oblige. * I mean, come on: it's a 20 line program that shows a 15x performance regression in a real-life, non-trivial application (http://www.flightgear.org), takes all of 5 commands to verify that can be copied right out of the source code, and even comes with a (IMHO) pretty insightful guess as to where the problem might lie. Most developers have erotic fantasies about this kind of bug report. Andy -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
