Re: [Tigervnc-devel] FLTK VNC Viewer Crashes on Debian 5.0
On Tue, 14 Jun 2011 16:30:14 -0400 Robert Goley rago...@rdasys.com wrote: Here is some output from gdb. I did this with and without debugging symbols in the fltk library. The huge one is the one with it. It doesn't seem to help much over the one that does not have it though. vncviewer segfaults and does not display any message before crashing. The log with fltk debug symbol kinda indicates that it might or should but it does not. I tested it in a VNC session. The DISPLAY was :99.0. This variable looks modifed at the bottom of that log file as well. Not sure if it is relevant though. Wanted you to know I did run it in a working valid display. Let me know if there is anything else I can get for you. Neither log was very helpful unfortunately. The small one didn't have enough detail, and the large one didn't crash. Please try again and see if you can reproduce the crash with debug info. Single stepping the entire things isn't necessary, just a full back trace when it hits the segfault. Rgds -- Pierre OssmanOpenSource-based Thin Client Technology System Developer Telephone: +46-13-21 46 00 Cendio ABWeb: http://www.cendio.com A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? signature.asc Description: PGP signature -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
[Tigervnc-devel] New vncviewer done
I've now reached a point where my near time todo list for vncviewer is empty. Except for Robert's issue, I have no known bugs at this time and the feature set should be good enough to replace the existing viewers. FLTK 1.3.0 is also out now, so we have a stable target for that dependency (modulo the massive patch we have). So please test away and try to break it. :) Rgds -- Pierre OssmanOpenSource-based Thin Client Technology System Developer Telephone: +46-13-21 46 00 Cendio ABWeb: http://www.cendio.com A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? signature.asc Description: PGP signature -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
[Tigervnc-devel] [ tigervnc-Bug Tracker-3305357 ] Enabling custom compression level on client crashes server
Bug Tracker item #3305357, was opened at 2011-05-20 19:00 Message generated for change (Comment added) made by bphinz You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1126848aid=3305357group_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: Brian Hinz (bphinz) Assigned to: Adam Tkac (atkac) Summary: Enabling custom compression level on client crashes server Initial Comment: Enabling custom compression causes the server to crash with the following log message: Fri May 20 18:39:07 2011 VNCSConnST: Client pixel format depth 24 (32bpp) little-endian rgb888 Fri May 20 18:40:11 2011 Connections: closed: 10.1.1.20::42053 (ZlibOutStream: deflate failed) SMsgWriter: framebuffer updates 148 SMsgWriter:copyRect rects 43, bytes 688 SMsgWriter:Tight rects 592, bytes 311570 SMsgWriter:raw bytes equivalent 18822164, compression ratio 60.410707 Segmentation fault Tried from both java and Windows exe. Tried DRC's latest nightly build as well as r4428 (1_1 branch) built on RHEL4. -- Comment By: Brian Hinz (bphinz) Date: 2011-06-17 09:21 Message: Seems good. No problems at all on RHEL4 for several days now, limited testing with RHEL5, but so far so good. I say go ahead and close it. -- Comment By: D. R. Commander (dcommander) Date: 2011-06-14 23:25 Message: Try the latest pre-release build at: http://www.virtualgl.org/DeveloperInfo/TigerVNCPreReleases Seems to be fixed as far as I can tell. If it works for you, I'll go ahead and close the issue. -- Comment By: Brian Hinz (bphinz) Date: 2011-06-14 15:20 Message: Can you try applying the patch that I uploaded (rev2) and see if it fixes the issue? I've been chugging along on RHEL4 (x86_64) for about 4 hours now, periodically changing the compression level, and have not been able to reproduce the error. I was not previously linking against the static libraries, but this time I added GNUTLS_FLAGS='/usr/lib64/libgnutls.a /usr/lib64/libgcrypt.a /usr/lib64/libgpg-error.a /usr/lib64/libgnutls-extra.a' --with-included-zlib to 'build-xorg build' (the --with-included-zlib should be redundant because of '-static', but I left it there for good measure). I won't be able to test this on RHEL5 until later tonight, but it seems to me that the error is more reproducible on RHEL5 than RHEL4(?). FYI, the patch alone did not cure the issue for me, so if it does work, it seems to be due to some combination of the patch and the requirement to link against the static libraries... Thanks, -brian -- Comment By: D. R. Commander (dcommander) Date: 2011-06-14 14:16 Message: I don't think it will. I link against static everything, and I still get the error. -- Comment By: Brian Hinz (bphinz) Date: 2011-06-14 10:06 Message: I'm still struggling to figure this out, but I wonder if it's related to which version of zlib we're linking against in the legacy build. I'm using the statically linked binaries produced by the build-xorg script, which links Xvnc against the system version of gnutls, and the in-tree version of zlib. However, the system version of gnutls already depend on the system version of zlib. The in-tree version of zlib appears to be 1.2.5, while the system version of zlib is 1.2.1 and 1.2.3 on RHEL4 and RHEL5 respectively. I'm going to try rebuilding and linking everything against the static versions of gnutls, libgcrypt, and libgpg-error along with the in-tree zlib and see if that helps. -- Comment By: Brian Hinz (bphinz) Date: 2011-06-02 19:53 Message: Don't commit it yet, there's still something wrong... Setting the compression level to 1 still crashes the server. -- Comment By: D. R. Commander (dcommander) Date: 2011-06-02 14:00 Message: Seems OK to me. I'd like to hear from Adam before committing it. -- Comment By: Brian Hinz (bphinz) Date: 2011-05-28 10:15 Message: Sorry, SYNC_FLUSH does seem to work. FULL_FLUSH causes a segfault when the client chooses compression level 1. Attaching new patch. -- Comment By: Brian Hinz (bphinz) Date: 2011-05-22 15:47 Message: Can someone review the attached patch? It seems to resolve the issue, but to be honest I don't know
Re: [Tigervnc-devel] FLTK VNC Viewer Crashes on Debian 5.0
I will try to get better detail for the crash. I will skip to the relevant section to keep it small too. I know the second log with library debugging seemed to show that it did not crash but that is not the case, it did crash. It never brought anything up either. I saw your other post on the new viewer. Was the FLTK source updated recently in the SVN? I can grab a later revision if that is the case. Also, do you know a good way to enable debugging for the FLTK lib? It kept using relative paths for source access and that was not providing details in gdb. Robert On 06/17/2011 04:59 AM, Pierre Ossman wrote: On Tue, 14 Jun 2011 16:30:14 -0400 Robert Goley rago...@rdasys.com wrote: Here is some output from gdb. I did this with and without debugging symbols in the fltk library. The huge one is the one with it. It doesn't seem to help much over the one that does not have it though. vncviewer segfaults and does not display any message before crashing. The log with fltk debug symbol kinda indicates that it might or should but it does not. I tested it in a VNC session. The DISPLAY was ":99.0". This variable looks modifed at the bottom of that log file as well. Not sure if it is relevant though. Wanted you to know I did run it in a working valid display. Let me know if there is anything else I can get for you. Neither log was very helpful unfortunately. The small one didn't have enough detail, and the large one didn't crash. Please try again and see if you can reproduce the crash with debug info. Single stepping the entire things isn't necessary, just a full back trace when it hits the segfault. Rgds -- Robert Goley FOSS Implementation Specialist Toll Free: (800) 338-4984 Local: (770) 479-7933 Fax: (770) 479-4076 www.openrda.com America's only Free Open Source fund accounting software company. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
Re: [Tigervnc-devel] FLTK VNC Viewer Crashes on Debian 5.0
Well, here is one small mystery solved. All the test programs for the FLTK library crash too. It is the library itself that is not working. The library and the vncviewer work fine when the extensions patch is not applied. I am not sure what changes are in there yet but they definitely break the lib on Debian 5.0. I will begin testing the vncviewer now that I can get a gui... Robert On 06/17/2011 10:18 AM, Pierre Ossman wrote: On Fri, 17 Jun 2011 09:27:27 -0400 Robert Goley rago...@rdasys.com wrote: I will try to get better detail for the crash. I will skip to the relevant section to keep it small too. I know the second log with library debugging seemed to show that it did not crash but that is not the case, it did crash. It never brought anything up either. I saw your other post on the new viewer. Was the FLTK source updated recently in the SVN? I can grab a later revision if that is the case. No, I haven't touched the local FLTK copy. Not much has changed in 1.3.0 though. Also, do you know a good way to enable debugging for the FLTK lib? It kept using relative paths for source access and that was not providing details in gdb. I've edited makeinclude and added -g to OPTIM in there. Then I've done touch FL/Fl.H and rebuilt the thing. Rgds -- Robert Goley FOSS Implementation Specialist Toll Free: (800) 338-4984 Local: (770) 479-7933 Fax: (770) 479-4076 www.openrda.com America's only Free Open Source fund accounting software company. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
