Floating point exception in 2.2 build 2204

Discussion in 'Installation and Configuration in Windows and Linux' started by ElPenguin, Oct 1, 2007.

  1. ElPenguin

    ElPenguin Bit poster

    Messages:
    4
    Hi all,

    I've built parallels' module against my current kernel after installation and when I go to run it I get the following:
    Code:
    [james@localhost ~]$ parallels
    
    
    Parallels Workstation 2.2  critical error! Send log file ( /usr/lib/parallels/bugreports/parallels-fault-121117.010907.7493.log ) to [email protected]
    
    
    /usr/bin/parallels: line 5:  7493 Floating point exceptionLD_LIBRARY_PATH=/lib:"${BASE_DIR}/lib" "${BASE_DIR}/`basename "${0}"`" $@
    Here is the logfile
    Code:
    -------------------------------------------------------------------------------
    Parallels Workstation 2.2  for Linux version 2.2 Build 2204.0 from 2007-09-18
    -------------------------------------------------------------------------------
    Received SIGFPE: Floating point exception
    	Access to fault address: 0xb79d2453
    	unknown signal sender: 1
    	Reason -  #0 [0xb7f29440]
     #1 /usr/lib/libqt-mt.so.3 [0xb79d2453]
     #2 /usr/lib/libqt-mt.so.3(_ZN12QPaintDevice13x11SetAppDpiXEii+0x20) [0xb79d24d0]
     #3 /usr/lib/libqt-mt.so.3(_Z16qt_init_internalPiPPcP9_XDisplaymm+0x244b) [0xb79b4cfb]
     #4 /usr/lib/libqt-mt.so.3(_Z7qt_initPiPPcN12QApplication4TypeE+0x36) [0xb79b5786]
     #5 /usr/lib/libqt-mt.so.3(_ZN12QApplication9constructERiPPcNS_4TypeE+0x87) [0xb7a1cea7]
     #6 /usr/lib/libqt-mt.so.3(_ZN12QApplicationC2ERiPPc+0x65) [0xb7a1d305]
     #7 /usr/lib/parallels/parallels [0x808dcb2]
     #8 /usr/lib/parallels/parallels [0x809043a]
     #9 /lib/libc.so.6(__libc_start_main+0xd8) [0xb74f8e18]
     #10 /usr/lib/parallels/parallels(_ZN6QFrame10paintEventEP11QPaintEvent+0x31) [0x808cff1]
    -------------------------------------------------------------------------------
    I've spoken with some of the foresight team (foresight is my linux distro) and they can't find anything wrong with Qt (which appears to be implicated). Does parallels perhaps require Qt4 and not state this?

    Thanks

    <edit>
    Code:
    [james@localhost ~]$ uname -a
    Linux localhost.localdomain 2.6.22.4-0.0.1.smp.gcc3.4.x86.i686 #1 SMP Tue Aug 21 15:56:37 EDT 2007 i686 i686 i386 GNU/Linux
    </edit>
     
    Last edited: Oct 1, 2007
  2. sandro

    sandro Parallels Developers

    Messages:
    512
    hmm,
    i have one approach around gcc version (couldn't you check version of gcc that using to compile module - if it 3.x then you must using 4.x i guess) but can't understand how qt symbols appeared at log file back trace
     
  3. ElPenguin

    ElPenguin Bit poster

    Messages:
    4
    Code:
    [james@localhost ~]$ gcc --version
    gcc (GCC) 3.4.4
    Appears I'm using GCC 3.4 after all. Thanks for the response though.
     
  4. sandro

    sandro Parallels Developers

    Messages:
    512
    so,
    switch gcc to 4.x. It must resolve issue.
     
  5. ElPenguin

    ElPenguin Bit poster

    Messages:
    4
    Using gcc 4.x will resolve my issue?

    I would have to rebuild my kernel for that and bootstrap gcc 4 onto my system (foresight won't have gcc 4 until their next major release).

    Why should it need gcc4?
     
  6. sandro

    sandro Parallels Developers

    Messages:
    512
    because providing by Parallels precompiled objective files were built under gcc 4.x
     
  7. ElPenguin

    ElPenguin Bit poster

    Messages:
    4
    Are there no modules built under gcc 3.4?

    It would be a really big deal to have to move to gcc4 to compile this module as the entire foresight toolchain is built under gcc 3.4

    Thanks for your response by the way, just what I needed to know.
     
    Last edited: Oct 1, 2007

Share This Page