[Interest] Running qemu as debug service provider in Qt Creator
Hi, I want to run a bare metal application in a QEMU environment and debug it with gdb using Qt Creator. But I can only see a limited predefined selection of debug providers, like openocd, j-link, ... Is there no way to run a custom command instead? I expected the "generic" provider to cover that usecase, but that seems to be something else. Thanks ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Running qemu as debug service provider in Qt Creator
On Tuesday, 5 October 2021 06:11:50 PDT Richard Weickelt wrote: > Hi, > > I want to run a bare metal application in a QEMU environment and debug it > with gdb using Qt Creator. But I can only see a limited predefined selection > of debug providers, like openocd, j-link, ... > > Is there no way to run a custom command instead? I expected the "generic" > provider to cover that usecase, but that seems to be something else. You can start it manually with qemu and tell it to stop before the first line of the application. Then tell Qt Creator to connect to the GDB server that qemu created. Debug > Start Debugging > Attach to Running Server -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel DPG Cloud Engineering ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Running qemu as debug service provider in Qt Creator
Hi, > You can start it manually with qemu and tell it to stop before the first line > of the application. Then tell Qt Creator to connect to the GDB server that > qemu created. > > Debug > Start Debugging > Attach to Running Server > Thanks, but it doesn't work. The "Attach to Running Server" dialog in Qt Creator is a bit confusing. Kit: My gcc-arm-none-abi kit (based upon the arm-none-eabi-gcc-8 toolchain shipped by the Qt maintenance tool). Server port: 1234 Local executable: The application ELF file Break at main is enabled I get "Unable to create debugging engine". My kit uses arm-none-eabi-gdb-py as the debugger. The device is a bare metal device and the debug server provider is set to None. If I choose the arm-none-eabi-gdb executable instead, I get "Failure during startup. Aborting. No debug server provider found for". Does the "attach to running server" even work for cross builds? ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Running qemu as debug service provider in Qt Creator
On Tuesday, 5 October 2021 09:53:55 PDT Richard Weickelt wrote: > Does the "attach to running server" even work for cross builds? It should. I haven't tested cross-architecture anything in nearly a decade, but I have tested cross-OS and it worked sometime in the last year or so. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel DPG Cloud Engineering ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
