Custom Query (981 matches)

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1209026880 (LWP 3753)] 0x009a5300 in pthread_mutex_lock () from /lib/libpthread.so.0
(gdb) bt
#0  0x009a5300 in pthread_mutex_lock () from /lib/libpthread.so.0
#1  0x00ab2846 in pthread_mutex_lock () from /lib/libc.so.6
#2  0x00184acc in g_logv () from /usr/lib/libglib-2.0.so.0
#3  0x00184c79 in g_log () from /usr/lib/libglib-2.0.so.0
#4  0x00184d5b in g_return_if_fail_warning () from /usr/lib/libglib-2.0.so.0
#5  0x004eacd2 in gdk_window_set_title () from /usr/lib/libgdk-x11-2.0.so.0
#6  0x004ef9cf in gdk_window_new () from /usr/lib/libgdk-x11-2.0.so.0
#7  0x004ccf4d in gdk_display_open () from /usr/lib/libgdk-x11-2.0.so.0
#8  0x004abaef in gdk_display_open_default_libgtk_only ()
   from /usr/lib/libgdk-x11-2.0.so.0
#9  0x059e2bff in gtk_init_check () from /usr/lib/libgtk-x11-2.0.so.0 #10 0x082a7d5c in ?? ()
#11 0xbff7fe78 in ?? ()
#12 0xbff7fe7c in ?? ()
#13 0x088fdc70 in ?? ()
#14 0x00000000 in ?? ()
(gdb)                          

Error 1723. DLL could not be run. (see attached)

Running 64-bit Linux client 5.9.11 on 64-bit Ubuntu 7.04 system, connecting to the net via a proxy. When trying to attach to the Worldcommunitygrid project, my system logs an error:

Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: SSLv2, Client hello (1):
Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol
Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: Expire cleared
Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: Closing connection #0
Sun May 27 20:45:22 2007||[http_debug] HTTP error: SSL connect error

Someone more familiar with HTTPS suggested that the error might have something to do with how the SSL version is being specified (i.e., by the boinc client).

Anyway, I was able to successfully attach (through the same proxy) to the WCG project on a (different) system running the 32-bit Linux client 5.10.0. That says to me that my WCG account, and my proxy, are working properly -- leaving the 64-bit client as the probable cause of my HTTPS connect problem.