Bug Tracker item #3397653, was opened at 2011-08-24 16:02
Message generated for change (Comment added) made by snmishra
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1126848&aid=3397653&group_id=254363

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: UN*X version
Group: 1.1.X
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Satya Narayan Mishra (snmishra)
Assigned to: Adam Tkac (atkac)
Summary: TigerVNC crash with SIGPIPE

Initial Comment:
I have only seen this crash when interacting with Motif programs. That may be 
because I mostly use Motif programs (CAD tools) or may be something to do with 
how Motif behaves.

I am using TigerVNC x86_64 version 1.1.0 on RHEL 4.6:

Linux HOST 2.6.9-67.ELsmp #1 SMP Wed Nov 7 13:56:44 EST 2007 x86_64 x86_64 
x86_64 GNU/Linux

Stacktrace
Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 182894042784 (LWP 30209)]
0x0000003ba48c0077 in writev () from /lib64/tls/libc.so.6
(gdb) bt
#0  0x0000003ba48c0077 in writev () from /lib64/tls/libc.so.6
#1  0x00000000006ba0fc in _XSERVTransSocketWritev ()
#2  0x00000000006b52e9 in FlushClient ()
#3  0x00000000006b593d in FlushAllOutput ()
#4  0x00000000006684fa in Dispatch ()
#5  0x000000000067e5fe in main ()


----------------------------------------------------------------------

Comment By: Satya Narayan Mishra (snmishra)
Date: 2011-08-24 20:11

Message:
I am using the build from sourceforge files section. I don't have
LD_ASSUME_KERNEL set. I DO have LD_LIBRARY_PATH set. 

Unfortunately, it is not reproducible. What I can I do to get a better
debug dump? Do you have debug symbols available for the binaries?
Alternatively, I can try making a debug build. Is Xvnc simpler to build now
that it is based on the newer Xorg?


ldd shows that only system libraries are used:

ldd Xvnc
        libpam.so.0 => /lib64/libpam.so.0 (0x0000003ba5d00000)
        libdl.so.2 => /lib64/libdl.so.2 (0x0000003ba4d00000)
        librt.so.1 => /lib64/tls/librt.so.1 (0x0000003ba9b00000)
        libm.so.6 => /lib64/tls/libm.so.6 (0x0000003ba4b00000)
        libc.so.6 => /lib64/tls/libc.so.6 (0x0000003ba4800000)
        libpthread.so.0 => /lib64/tls/libpthread.so.0 (0x0000003ba5100000)
        libaudit.so.0 => /lib64/libaudit.so.0 (0x0000003ba6300000)
        /lib64/ld-linux-x86-64.so.2 (0x0000003ba4400000)


----------------------------------------------------------------------

Comment By: Brian Hinz (bphinz)
Date: 2011-08-24 19:54

Message:
I don't have access to Laker, but I use IC5141 over vnc daily.  Can you
check to make sure that LD_LIBRARY_PATH and LD_ASSUME_KERNEL are NOT set in
the shell that you launched Xvnc from?  Also, is this reproducible?  If so,
please can give me some steps to reproduce it.  Did you build Xvnc from
source?

Thanks,
-brian

----------------------------------------------------------------------

Comment By: Satya Narayan Mishra (snmishra)
Date: 2011-08-24 17:11

Message:
I have seen the crash with both Cadence IC 5.1.41 and Springsoft Laker
3.2v4p2.

----------------------------------------------------------------------

Comment By: Brian Hinz (bphinz)
Date: 2011-08-24 16:45

Message:
Which tools cause this crash?  I'm using 1.1 with a variety of different
EDA tools and have never seen this.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1126848&aid=3397653&group_id=254363

------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management 
Up to 160% more powerful than alternatives and 25% more efficient. 
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

Reply via email to