On Mon, 21 Jul 2003, mtbramo wrote:

> The version of curl is 7.10.2 (but I have tried on 7.10.5 and we have the
> same problem).

You should still be using 7.10.5, as it will contain less other bugs that may
or may not confuse the debugging.

> No, CURLOPT_NOSIGNAL is not set to TRUE. But I don't think that it will
> change something because I use curl like a static library for an executable
> and in this executable (I need to catch the exception) I have define a
> signal handler.

You should of course know what you need and what to use, I just mentioned this
since signals and threads normally don't match very well.

> >>#4 0x4002a8d5 in pthread_sighandler (signo=11, ctx={gs = 231, __gsh =
> >>0, fs = 0, __fsh = 0, es = 43, __esh = 0, ds = 43, __dsh = 0, edi =
> >>136608544, esi = 1211102695, ebp = 1211102564, esp = 1211102412, ebx =
> >>1181771448, edx = 135986336, ecx = 0, eax = 16, trapno = 14, err = 4,
> >>eip = 134773073, cs = 35, __csh = 0, eflags = 66118, esp_at_signal =
> >>1211102412, ss = 43, __ssh = 0, fpstate = 0x482ff250, oldmask =
> >>2147483648, cr2 = 16}) at signals.c:97
> >>#5 <signal handler called>
> >>#6 0x08087951 in Curl_connecthost (conn=0x467066b8,
> >>remotehost=0x81afca0, port=8080, sockconn=0x46706958, addr=0x482ff598,
> >>connected=0x482ff5e7 "") at connect.c:579

I take it that frame #6 here is what needs attention. If you get this crash on
7.10.5, what line number does this "crash" on then?

-- 
 Daniel Stenberg -- curl: been grokking URLs since 1998
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0