On Thu, Apr 13, 2006 at 12:24:56PM -0400, Christopher Faylor wrote:
>On Thu, Apr 13, 2006 at 05:48:22AM -0700, Gary Zablackis wrote:
>>> The exception handler is supposed to be initialized
>>> in
>>> _cygtls::init_thread which is called from
>>> initialize_main_tls.
>>> Why is that not happening?
>
On Thu, Apr 13, 2006 at 05:48:22AM -0700, Gary Zablackis wrote:
>> The exception handler is supposed to be initialized
>> in
>> _cygtls::init_thread which is called from
>> initialize_main_tls.
>> Why is that not happening?
>
>It does happen. However, later on when the program calls dlopen ()
>(wh
> The exception handler is supposed to be initialized
> in
> _cygtls::init_thread which is called from
> initialize_main_tls.
> Why is that not happening?
>
> cgf
>
It does happen. However, later on when the program
calls dlopen () (which will happen, e.g., when a
python program imports a dll),
On Wed, Apr 12, 2006 at 06:53:33AM -0700, Gary Zablackis wrote:
>The code below corrects this problem.
>
>CHANGELOG:
>2006-04-11 Gary Zablackis [EMAIL PROTECTED]
> * (Thanks to Bernhard Loos for pointing the way)
> * dll_init.cc (dll_dllcrt0()): install Cygwin
>exception handler so that Cygwin can
On 12 April 2006 14:54, Gary Zablackis wrote:
> +++ dll_init.cc 12 Apr 2006 13:41:24 -
> @@ -351,6 +351,8 @@ dll_list::load_after_fork (HANDLE
> parent
^^^
> extern "C" int
> dll_dllcrt0 (HMODULE h, per_process *p)
> {
> + _my_tls.init_exception_handler
> (_cygtls::handle_exception
--- Christopher Faylor
<[EMAIL PROTECTED]> wrote:
> We've moved out of the realm of a "patch" here.
> Please use the main
> cygwin list to report and diagnose problems.
>
> cgf
>
OK
Thanks,
Gary
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail ha
On Thu, Mar 09, 2006 at 07:04:23AM -0800, Gary Zablackis wrote:
>--- Brian Dessent <[EMAIL PROTECTED]> wrote:
>>If you are trying to track down why you get a SIGSEGV in
>>pthread_key_create while running your app in gdb you are wasting your
>>time. This is not a fault, it is expected and normal.
--- Brian Dessent <[EMAIL PROTECTED]> wrote:
> If you are trying to track down why you get a
> SIGSEGV in
> pthread_key_create while running your app in gdb you
> are wasting your
> time. This is not a fault, it is expected and
> normal. Search the
> archives.
>
> Brian
>
In this case, the fa
Gary Zablackis wrote:
> 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
> calli
--- Christopher Faylor
<[EMAIL PROTECTED]> 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
On Fri, Mar 03, 2006 at 09:13:53AM -0800, Gary Zablackis wrote:
>--- Christopher Faylor
><[EMAIL PROTECTED]> wrote:
>
>>The "efault.faulted()" two lines above your change is supposed to catch
>>NULL dereferences. I suspect that you were probably misled by the fact
>>that gdb might show a SEGV in t
--- Christopher Faylor
<[EMAIL PROTECTED]> wrote:
> The "efault.faulted()" two lines above your change
> is supposed to catch
> NULL dereferences. I suspect that you were probably
> misled by the fact
> that gdb might show a SEGV in this function but that
> is to be expected
> (see lots of discus
On Thu, Mar 02, 2006 at 10:11:39AM -0800, Gary Zablackis wrote:
>Since installing Cygwin1.dll v 1.5.19-4, I have a problem with the
>computer algebra system SAGE dying at startup with no error messages
>(i.e. I get returned to the bash prompt with no messages of any sort).
>I tracked the problem d
13 matches
Mail list logo
