This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
Re: Bug in dlopen() (or following) code in Cygwin1.dll v 1.5.19-4
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: cygwin-talk at cygwin dot com
- Date: Thu, 16 Mar 2006 11:32:10 -0500
- Subject: Re: Bug in dlopen() (or following) code in Cygwin1.dll v 1.5.19-4
- References: <441988A6.7010609@huarp.harvard.edu> <002201c64915$5d9f2710$a501a8c0@CAM.ARTIMI.COM>
- Reply-to: cygwin-talk at cygwin dot com
- Reply-to: The Cygwin-Talk Malingering List <cygwin-talk at cygwin dot com>
On Thu, Mar 16, 2006 at 04:19:14PM -0000, Dave Korn wrote:
>Take a /look/ at the source for myfault::faulted in cygtls.h, it calls
>out to _cygtls::setup_fault, which calls _sjfault, which appears to be
>a q'n'd hacked-up version of setjmp in a context where it's going to
>get called back by an SEH handler. So IIUIC, calling 'efault.faulted'
>will catch any exception that happens from the point of the call until
>the point where the efault object goes out of scope and gets destructed
>and will cause execution to jump back to the if... clause.
What is this "take a /look/" thing you're talking about? What kind of
photonic voodoo are you proposing?
I've wasted a full day trying to understand what you're talking about.
What is the problem with understanding this code without looking at it?
cgf