Results 1 to 4 of 4

Thread: Incompatibility with WRQ Reflection X version 14

  1. #1
    Junior Member
    Join Date
    Mar 2007
    Posts
    2

    Incompatibility with WRQ Reflection X version 14

    Whenever I try to start any version of (Linux 32) totalview from a session that uses WRQ Reflection X version 14, totalview immediately fails with a message like:

    Fatal: Unhandled exception in program *** (Location of Totalview Program ***
    Exception: exMathError (ID 46)
    Math error: floating point exception
    Thrown From: file csfpe.cc line 72
    Program aborting immediately!

    This appears to happen when totalview is initializing and attempting to establish X connectivity. I have no way to determine whether Reflection is sending illegal information to totalview, or just sufficiently unusual information that totalview cannopt cope. One possible cause is a buffer overflow when receiving information from Reflection.



  2. #2
    Senior Member
    Join Date
    Jun 2006
    Location
    Natick MA
    Posts
    145

    Re: [DavidSachs] Incompatibility with WRQ Reflection X version 14

    This problem was reported to TotalView Customer Support. The problem does not occur with WRQ Reflection X version 12 or 13. The easiest way to work around this issue is to use a different X server. We would suggest using Tight VNC or perhaps Cygwin.
    Josh Carlson

  3. #3
    Junior Member
    Join Date
    Mar 2007
    Posts
    2

    Re: [Josh-TotalView-Tech] Incompatibility with WRQ Reflection X version 14

    The problem was due to a bug in Reflection.

    The latest patched version of Reflection works properly with Totalview.

  4. #4

    Recent issues

    We've had a few reports of other people running into this recently when trying to run TotalView on a cluster with the windows reflecting back to their laptop, usually a Macbook. Since the google search seems to lead them to this page, I'd like to note that rebooting the laptop seems to fix the problem. This appears to happen after they've been using TotalView a number of times recently, all working okay. But once it gets into this state, a reboot seems to be the only workaround found so far. So save anything local that might be affected, and reboot.

    Regards,
    Pete Thompson
    TotalView Customer Services

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •