Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Special Interest Groups
  3. QtonPi
  4. Simple QtWebKit Application Crashes w/ Segmentation Fault
QtWS25 Last Chance

Simple QtWebKit Application Crashes w/ Segmentation Fault

Scheduled Pinned Locked Moved QtonPi
6 Posts 3 Posters 4.4k Views
  • 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.
  • B Offline
    B Offline
    brporter
    wrote on last edited by
    #1

    DISCLAIMER: I'm an absolute newb, and I am happy to RTFM if this is an obvious question, just point me where. :)

    I've got Qt5 cross compiled for the Raspberry Pi. Simple QML apps (display "Hello World!" in the middle of the screen) work just fine (I'm using the eglfs platform plugin). WebKit crashes immediately, though.

    Code:

    @
    #include <QApplication>
    #include <QWebView>

    int main(int argc, char *argv[])
    {
    QApplication app(argc, argv);
    QWebView v;

    v.setUrl(QUrl("http://www.bryanporter.com"));
    v.show();
    
    return app.exec();
    

    }
    @

    Works just long enough to start rendering the background of my web page, then crashes with a segmentation fault. Wiring up a remote debugger shows that the signal being received is SIGILL (illegal instruction).

    I'm not sure next steps to debug... any pointers are much appreciated!

    Bryan

    1 Reply Last reply
    0
    • B Offline
      B Offline
      brporter
      wrote on last edited by
      #2

      A bit more info - running the app on the Pi under GDB, I'm receiving the following detail:

      @
      Program received signal SIGILL, Illegal instruction.
      0xade645e0 in ?? () from /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.0.0
      @

      1 Reply Last reply
      0
      • L Offline
        L Offline
        LongChair
        wrote on last edited by
        #3

        I am having exactly the same issue with qt 5.4 build.
        I made a very simple testcase like yours and getting the same result.

        did you find a way to fix that one ?

        1 Reply Last reply
        0
        • L Offline
          L Offline
          LongChair
          wrote on last edited by
          #4

          I found at that SIGILL was a normal thing as libcrypto will test cpus. hitting 'c' in dgb just continues and this doesnt crash at runtime.

          Although for me in current state of Qt5.4, I am experiencing a crash with whatever app uses the QWebView. it happens with some very basic samples and the qtwebkit browser sample as well.

          1 Reply Last reply
          0
          • E Offline
            E Offline
            EricZ89
            wrote on last edited by
            #5

            My qtwebkit-example 'browser' will crash with a 'Segmentation Fault' error. I too am using Qt5.4.0.

            I am using:
            -Qt5.4.0(eglfs)-qtwebkits-example-example
            -Built in an OpenEmbedded environment
            -Cross-compiled with arm-gnueabihf 4.7 (linaro)
            -TI am335x ARM processor
            -Using TI SDK 5_01_01_01 for graphic drivers and library support.

            Are you passing any extra export variables or arguments when running the browser example? Did you ever find a solution to your problem?

            1 Reply Last reply
            0
            • E Offline
              E Offline
              EricZ89
              wrote on last edited by
              #6

              My qtwebkit-example 'browser' will crash with a 'Segmentation Fault' error. I too am using Qt5.4.0.

              I am using:
              -Qt5.4.0(eglfs)-qtwebkits-example-example
              -Built in an OpenEmbedded environment
              -Cross-compiled with arm-gnueabihf 4.7 (linaro)
              -TI am335x ARM processor
              -Using TI SDK 5_01_01_01 for graphic drivers and library support.

              Are you passing any extra export variables or arguments when running the browser example? Did you ever find a solution to your problem?

              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