Mail Archives: cygwin/2009/07/17/14:32:09
On Fri, Jul 17, 2009 at 06:36:16PM +0200, Corinna Vinschen wrote:
>On Jul 17 11:44, Christopher Faylor wrote:
>> On Fri, Jul 17, 2009 at 05:29:20PM +0200, Corinna Vinschen wrote:
>> >On Jul 17 15:23, Dave Korn wrote:
>> >> Corinna Vinschen wrote:
>> >> > Do we have to take other handlers than the OS handlers and the Cygwin
>> >> > handlers into account? Cygwin apps don't install SEH handlers, do
>> >> > they? Or do C++ apps?
>> >>
>> >> Nope, they don't, but that will probably not be the case forever, there are
>> >> (long-term) moves afoot to get SEH support into the compiler. However, we're
>> >> in early startup-and-init here; we don't need to worry about what the
>> >> application will do once it finally gets going.
>> >
>> >Sorry, but AFAICS we are not in early startup-and-init. The threads.dll
>> >library is a run-time loaded DLL via dlopen due to the
>> >
>> > use threads;
>> >
>> >statement in the script. This situation can occur at any point
>> >during the runtime of an application.
>>
>> Right, and I don't know how you could make the claim that Cygwin apps
>> don't install SEH handlers. We can't possibly know how every Cygwin app
>
>I didn't make a claim, I asked.
You didn't make the claim. I was responding to "Nope, they don't"
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
- Raw text -