X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Thu, 23 Jul 2009 10:40:39 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: [1.7] Updated: libsigsegv-2.6-1 Message-ID: <20090723144038.GA11519@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4A678AC7.7090303@x-ray.at> <4A6854F8.4060204@byu.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A6854F8.4060204@byu.net> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Thu, Jul 23, 2009 at 06:18:00AM -0600, Eric Blake wrote: >According to Reini Urban on 7/22/2009 3:55 PM: >>I've updated libsigsegv to 2.6-1 and added a shared library in >>libsigsegv0-2.6-1 I hope this solves the SEH corruption issue a little >>bit, as discussed at http://cygwin.com/ml/cygwin/2009-07/msg00639.html > >Nope, 2.6 still has the SEH misuse bug. But if you want to rebuild >from a git repository, my patches are now available to fix the SEH >handling (although I recommend building against cygwin snapshot >20090722 or newer; building against cygwin 1.7.0-51 will detect that >si_addr is still broken, and pick up baggage related to cygwin 1.5 but >not necessary for the latest cygwin1.dll). I only lightly tested a >shared library with my patches. Although the testsuite passed while >using the shared library, I am still wondering if there could be a >problem at program shutdown if the shared library is removed from >memory without modifying its SEH handler back to cygwin's handler, but >I don't have any test case that provoked that scenario. > >$ git pull git://repo.or.cz/libsigsegv/ericb.git master I'm still mystified as to how a package which uses automatic variables to deal with a stack overflow situation could claim to be handling stack overflow. I really don't like the games this package plays. I'm halfway tempted to just make it nonfunctional in Cygwin. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple