On Thu, May 31, 2012 at 04:01:43PM -0500, Ryan C. Underwood wrote: > > How can I "bisect" Cygwin i.e. by setting a certain date at which to > install packages that were current as of that date, and checking if > problem remains, so as to track down the date a problem/different > behavior was introduced sometime in the past year? Actually, if I > could start with the Cygwin DLLs themselves, that would probably get > me to the bottom of it.
I located the problem, it came in between the Time Machine 2012/02/04 and 2012/02/05 archives. Unfortunately, this looks like a major release for Cygwin happened on that day: good: CYGWIN_NT-6.1 MYPC 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin bad: CYGWIN_NT-6.1 MYPC 1.7.10(0.259/5/3) 2012-02-05 12:36 i686 Cygwin I tried diffing the CVS by tags but it doesn't look like 1.7.9 was tagged, or else the tags were removed as obsolete. Any suggestions as to the best way to dig into the differences here? -- Ryan C. Underwood, <[email protected]>
signature.asc
Description: Digital signature
