Why donĀ“t you just use the Receiver for HTML5? With regard to your crash, do you have a backtrace handy?
2016-02-25 14:03 GMT+01:00 Patrick Welche <pr...@cam.ac.uk>: > On Wed, Feb 03, 2016 at 07:31:35PM +0100, Jose Luis Rodriguez Garcia wrote: >> On Tue, Feb 2, 2016 at 4:17 AM, Eric Haszlakiewicz <e...@nimenees.com> wrote: >> > On 2/1/2016 3:51 PM, Jose Luis Rodriguez Garcia wrote: >> >> >> > Have you tried downloading a newer version of the client from Citrix's >> > site? >> >> I have just tried the last version of citrix as you told me. >> >> It solves the problem of the certificate (the old version didn't >> understand the CA from Godaddy, but it coredumps at the startup. >> >> I copy backtrace/registers and output from ktruss: > ... >> 2412 2412 wfica RET writev 324/0x144 >> 2412 2412 wfica CALL poll(0xbfbff418,1,0xffffffff) >> 2412 2412 wfica RET poll 1 >> 2412 2412 wfica CALL read(3,0x8264a38,0x1000) >> 2412 2412 wfica GIO fd 3 read 32 bytes >> "\^A\^B8\^B\0\0\0\0002\0`\^A\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0" >> 2412 2412 wfica RET read 32/0x20 >> 2412 2412 wfica CALL read(3,0x8264a38,0x1000) >> 2412 2412 wfica RET read -1 unknown errno 35 >> 2412 2412 wfica CALL read(3,0x8264a38,0x1000) >> 2412 2412 wfica RET read -1 unknown errno 35 >> 2412 2412 wfica CALL gettimeofday(0xbfbff8bc,0) >> 2412 2412 wfica RET gettimeofday 0 >> 2412 2412 wfica CALL gettimeofday(0xbfbff83c,0) >> 2412 2412 wfica RET gettimeofday 0 >> 2412 2412 wfica CALL gettimeofday(0xbfbff7dc,0) >> 2412 2412 wfica RET gettimeofday 0 >> 2412 2412 wfica CALL socketcall(9,0xbfbff5f0) >> 2412 2412 wfica MISC send: 16, >> 06000000ffffffe87cffffffdcffffffb92200000000000000 >> 2412 2412 wfica MISC msghdr: [name=0x0, namelen=0, >> iov=0xf323bc84, iovlen=1, control=0x0, controllen=3226819742, flags=0] >> 2412 2412 wfica GIO fd 6 wrote 34 bytes >> >> "\^W\^C\^A\0\^]\\\M-f`WIH*\M^F\M-%\^X\M-y\M^@9\M-t({In39$\M-!\^[\M^TNc\M^N/\M-_" >> 2412 2412 wfica RET socketcall 34/0x22 >> 2412 2412 wfica CALL gettimeofday(0xbfbff6fc,0) >> 2412 2412 wfica RET gettimeofday 0 >> 2412 2412 wfica CALL gettimeofday(0xbfbff68c,0) >> 2412 2412 wfica RET gettimeofday 0 >> 2412 2412 wfica CALL gettimeofday(0xbfbff6fc,0) >> 2412 2412 wfica RET gettimeofday 0 >> 2412 2412 wfica PSIG SIGSEGV SIG_DFL: code=SEGV_MAPERR, >> addr=0x92ee48c6, trap=14) >> 2412 2459 wfica RET select -1 unknown errno 4 >> 2412 2412 wfica NAMI "wfica.core" > > I am seeing this too. Essentially there are a load of calls to > linux_sys_recvmsg which returns 35 (EAGAIN). The last round looks like > > got here linux_sys_recvmsg 834 (do_sys_recvmsg=35) > got here linux_select1 894 selcommon=0 > got here linux_sys_select 844 > got here linux_sys_recvmsg 815 > got here linux_to_bsd_msghdr 455 > got here linux_sys_recvmsg 820 > got here linux_to_bsd_msg_flags 279 > msg_name=0x0 > msg_namelen=0 > msg_iov=0x7f7fffffebd0 > msg_iov=0x7f > msg_control=0x7f7fffffec20 > msg_controllen=80 > msg_flags=4000000 > control=0xffffffff80586483 > from=0xfffffe804534be58 > got here linux_sys_recvmsg 834 (do_sys_recvmsg=35) > got here linux_select1 894 selcommon=4 > pid 3382 (wfica), uid 1000: exited on signal 11 (core dumped) > > So it seems that after too many retries, a timer fires and kills the > process (linux_select1()). I suppose the underlying issue is with > linux_sys_recvmsg, but how can you find out what? > > Cheers, > > Patrick