This is the mail archive of the
cygwin-patches
mailing list for the Cygwin project.
Re: Patch for silent crash with Cygwin1.dll v 1.5.19-4
- From: Gary Zablackis <gzabl at yahoo dot com>
- To: cygwin-patches at cygwin dot com
- Date: Mon, 6 Mar 2006 06:14:11 -0800 (PST)
- Subject: Re: Patch for silent crash with Cygwin1.dll v 1.5.19-4
--- Christopher Faylor
<cgf-no-personal-reply-please@cygwin.com> wrote:
> You have missed how efault.faulted() is supposed to
> be operating and,
> AFAICT, *does* operate throughout the Cygwin DLL.
> It really is supposed
> to be catching NULL dereferences.
>
> It's possible of course, that there is something
> wrong with efault.faulted()
> but that doesn't mean we need to extra code around
> efault.faulted. It means
> that efault.faulted needs to be fixed.
>
> i.e., we need to fix the problem not the symptom.
>
> cgf
>
I did some more research over the weekend and my
problem seems to only come when loading a dll via
dlopen() and run_ctors() is called from dll:init() and
pthread_key_create() is called during the time that
run_ctors() is active. I still have not found who is
calling pthread_key_create(), but will be working on
this as time permits this week.
It's been several years since I did any assembly
language coding, so I have to study what's going on
when efault.faulted() returns non-zero - and figure
out how to get gdb to step through the assembly code.
Thanks,
Gary
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com