Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 12 Jun 2002 08:32:39 -0400 From: rich-paul AT rich-paul DOT net To: cygwin AT cygwin DOT com Subject: Re: Am I missing something? Message-ID: <20020612083239.A11421@monster.rich-paul.net> References: <20020612002933 DOT A10609 AT monster DOT rich-paul DOT net> <20020612052910 DOT GA21519 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.16i In-Reply-To: <20020612052910.GA21519@redhat.com>; from cgf-cygwin@cygwin.com on Wed, Jun 12, 2002 at 01:29:10AM -0400 X-Operating-System: Linux monster 2.4.17-SMPs Sorry, I guess my searches missed the stack trace, as it was in an attachment. And I didn't thing to search on 'miserably'. *G* Anyway, I'll switch over to the CVS tree. And I'll try to get the cultural stuff right, this is very differant in that respect from developing as a consultant. On Wed, Jun 12, 2002 at 01:29:10AM -0400, Christopher Faylor wrote: > On Wed, Jun 12, 2002 at 12:29:33AM -0400, linguist-cygwin AT rich-paul DOT net wrote: > >I had to change wincap.{cc,h} in order to get the 6/9/2002 snapshot to > >work for me. Without that, every cygwin program would segfault before > >entering main, due to trying to access wincapc in the pthreads > >initialization code. > > > >It seems odd, however, that there's been no discussion of such a > >problem on this list or the cygwin developer's list. > > http://cygwin.com/ml/cygwin/2002-06/msg00528.html > > >Thus my question: have I missed something? Or am I the only one trying > >snapshots? > > > >Anyway, my patch is here, FWIW: > > I appreciate the fact that you are trying snapshots but you really > should check that you are actually running the *latest* snapshot. > > I also very much appreciate the fact that you're providing patches but, > for the patches to be useful, it's usually safer to generate them > against cvs. If you're rebuilding cygwin, you'll see fixes much more > quickly if you update from cvs. > > Anyway, in this case, the problem was discovered and fixed on > 2002-06-10. > > cgf > -- > Please do not send me personal email with cygwin questions. > Use the resources at http://cygwin.com/ . > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Bug reporting: http://cygwin.com/bugs.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > -- Got freedom? Vote Libertarian: http://www.lp.org -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/