Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. Qt 4.8.0 SegFault on App Startup
Forum Updated to NodeBB v4.3 + New Features

Qt 4.8.0 SegFault on App Startup

Scheduled Pinned Locked Moved Installation and Deployment
1 Posts 1 Posters 915 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    DannO
    wrote on last edited by
    #1

    I am using Solaris 10 x86 and compiled Qt 4.8.0 with GCC 4.7.1 (which I also compile for Solaris). When I run an app that is dynamically linked against the Qt I compiled, I can make the application core during startup. If I change directories into the location of my binary, the application runs fine. If I used the full path to start the application, the application will segfault on startup. It looks like it is passing the full name of the application (argv[ 0 ]) and eventually coring in QString. The line in QString where it cores is here:
    http://qt.gitorious.org/qt/qt/blobs/f33b28d27a8e738fa93a45f44445d0fe255810b0/src/corelib/tools/qstring.cpp#line3838

    This is just inside a QT_ALWAYS_HAVE_SSE2 block. Does this mean SSE2 is not supported on my OS. Also, if I compile Qt without SSE2 should I also disable use of other SSE versions (i.e. SSE3, SSE4, etc...)?

    Thanks!

    1 Reply Last reply
    0

    • Login

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Get Qt Extensions
    • Unsolved