Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Debugging of Android applications with creator

Debugging of Android applications with creator

Scheduled Pinned Locked Moved Solved Mobile and Embedded
android gdbandroid
3 Posts 2 Posters 1.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.
  • K Offline
    K Offline
    koahnig
    wrote on last edited by
    #1

    I tried to debug an application compiled debug settings through creator on windows 10 64 bit.

    Currently I am using Qt 5.11.3 as listed here
    0_1547755320025_f35c7c2a-7176-4f91-90e2-79041da64d96-image.png

    with armeabi-v7a the virtual device is not even starting. Therefore I have addd already the android for x86 kit. This does start the virtual device, but debugging is not possible.

    I have checked and the debug server as listed for android for x86 is in place and can be started on command line.

    This is the output to the application pane in creator

    21:07:11: Debugging starts
    I art     : Not late-enabling -Xcheck:jni (already on)
    W art     : Unexpected CPU variant for X86 using defaults: x86
    W ActivityThread: Application org.qtproject.example.satelliteinfo is waiting for the debugger on port 8100...
    I System.out: Sending WAIT chunk
    I art     : Ignoring second debugger -- accepting and dropping
    Could not load shared library symbols for 137 libraries, e.g. /system/lib/libcutils.so.
    Use the "info sharedlibrary" command to see the complete listing.
    Do you need "set solib-search-path" or "set sysroot"?
    

    and this is the output shown on virtual device:
    0_1547755754485_92ad12e3-9fd6-428b-b791-2e4165023e87-image.png

    Vote the answer(s) that helped you to solve your issue(s)

    1 Reply Last reply
    0
    • K Offline
      K Offline
      koahnig
      wrote on last edited by
      #2

      The problem could be solved by updating the Android suite to newest version.

      Vote the answer(s) that helped you to solve your issue(s)

      1 Reply Last reply
      2
      • S Offline
        S Offline
        Seongnam Jee
        wrote on last edited by
        #3

        on Qt Creator
        in Tools > Options > Debugger > GDB > Additional Attatch Commands
        ex. Insert "set solib-search-path /opt/Qt/5.12.1/android_x86/lib"

        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