Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#54 segmentation fault

open
nobody
None
5
2005-01-12
2005-01-12
Anonymous
No

I always get that message when first connecting, after
that, it works. BTW, I use 10.2.8 and start
osxvnc-server via the console.

Discussion

  • Logged In: YES
    user_id=631278

    It's ok to launch the server in console mode, you might try launching
    using the link that is provided directly inside the app wrapper:

    OSXvnc.app/osxvnc-server

    Outside of that we don't have anything to suggest. We aren't seeing this
    bug here at Redstone although we have heard reports of it in the field
    anything more you can tell us about the bug will help us to track it down.

     
  • Logged In: YES
    user_id=631278

    We have worked dilligently to try to recreate this problem but we can not
    get it to happen on 10.2.8 or 10.3.7.

    Since you are the only person reporting this behavior and you are seeing
    it in the GUI app and the command line app it's likely that something on
    your system is interfering with OSXvnc's ability to function.

    First question, are you running any tools using APE from Unsanity.org?
    Second are you running any other third party utilites that would effect
    the system or other applications across the board?

    If you have either an OSXvnc.app.log or an OSXvnc-server.log in your ~/
    Library/Logs/CrashReporter directory please send those to us.

    If you have access to another MacOS X system it would be helpful for
    you to try OSXvnc there also.

     
  • Daniel Brice
    Daniel Brice
    2005-05-19

    Logged In: YES
    user_id=585858

    I also get a Segmentation Fault regularly. Mine happens after leaving VNC
    for some time. It probably happens on average about once for every 3
    hours of use.

    I have a Crash report, you can get it at:
    http://users.dls.net/~dburke/OSXvnc-crash-1.txt

    Let me know if you want anymore details - I'd be happy to help

     
  • Logged In: YES
    user_id=631278

    These crash logs are valuable and they indicate a problem with the
    TIGHT encoding, you might try using a different encoding and see if the
    problem goes away, then we can really focus our search on that section
    of the code.

    --
    Jonathan Gillaspie

     
  • Daniel Brice
    Daniel Brice
    2005-05-20

    Logged In: YES
    user_id=585858

    I was able to get a Segmentation Fault even after switching
    to use Raw encoding. The crash log is at:
    http://users.dls.net/~dburke/OSXvnc-crash-3-Raw.txt

    I know I was using raw because the OSXvnc log stated:
    ENCODING: Raw for client X.X.X.X

     
  • Daniel Brice
    Daniel Brice
    2005-05-23

    Logged In: YES
    user_id=585858

    Another Segmentation Fault using Raw encoding:

    http://users.dls.net/~dburke/OSXvnc-crash-4-Raw.txt

    Any idea's on what else I can do to help solve this one?

    Thanks,
    Dan.

     
  • Logged In: YES
    user_id=631278

    The latest crashes are in the translation logic, if your client allows you to do
    "server native" resolution that might help it. What client are you using
    because we aren't used to seeing these kinds of crashes out of the core
    VNC engine. Also anything else about your setup that might be considered
    "non-standar", ie running FINK tools, APE or other system wide extensions?

     
  • Daniel Brice
    Daniel Brice
    2005-05-23

    Logged In: YES
    user_id=585858

    I'm running my client at the native resolution of the server
    1280x768.

    My client is tightvnc-1.2.9-1 running on a RedHat 8.0 Linux
    box. It's a pretty old (came with RH8.0). I also connect to
    Solaris machines with VNC with it as a client for years, and
    it's not had one problem in my memory.

    I have seen my VNC client have problems when connecting to a
    PC running UltraVNC many times, but in those cases it
    complained a problem with the data that UltraVNC was
    sending, and neither the client or server actually crashed.

    I was running APE at one point, but I uninstalled it a while
    ago. Is there any easy way for me to list other system wide
    extensions like that?

    Dan.

     
  • Daniel Brice
    Daniel Brice
    2005-05-23

    Logged In: YES
    user_id=585858

    Here's the output from my VNC client upon startup... doesn't
    look like there's much translation being done:

    vncviewer 192.168.X.XX:X -v -encodings Raw
    VNC server supports protocol version 3.3 (viewer 3.3)
    Desktop name "XXXXXXX"
    Connected to VNC server, using protocol version 3.3
    VNC server default format:
    32 bits per pixel.
    Most significant byte first in each pixel.
    True colour: max red 255 green 255 blue 255, shift red 16
    green 8 blue 0
    Using default colormap which is TrueColor. Pixel format:
    32 bits per pixel.
    Least significant byte first in each pixel.
    True colour: max red 255 green 255 blue 255, shift red 16
    green 8 blue 0
    Using shared memory PutImage

    Dan.

     
  • Logged In: YES
    user_id=631278

    Yup, it looks like the only translation is the Big-Endian to Little-Endian logic.
    We haven't done too much with that but haven't received any major
    complaints. It may only trigger in Raw. You might try Hextile encoding or
    ZRLE which generally has the most "mileage", we'll continue to look and see
    if there are patches which can be applied to those areas of the code.

     
  • Logged In: YES
    user_id=631278

    I'm highly suspicious that it might be a conversion issue if the server is
    being asked to feed the bytes to a little-endian machine, we hardly ever
    see it when connecting from Mac OS X clients.

    Of course this is something we'll need to be addressing given the latest
    announcements from Apple.

    If anyone is endeavoring to search these problems out, you might try
    comparing to some of the later TightVNC code which is the codebase
    that OSXvnc was branched from originally