Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. GammaRay: experiences?
Qt 6.11 is out! See what's new in the release blog

GammaRay: experiences?

Scheduled Pinned Locked Moved Qt Creator and other tools
3 Posts 1 Posters 4.3k 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.
  • A Offline
    A Offline
    andre
    wrote on last edited by
    #1

    I am trying to use GammaRay, but I can't get it to work.

    I have build and installed the software. When starting, I get a dialog with some listed processes (Qt based applications, but not all). However, when I Attach to one of these applications, the screen disapears and nothing else seems to happen. GammaRay is still running, but not showing any UI. I am interested to hear experiences from others in how they manage to use this tool.

    1 Reply Last reply
    0
    • A Offline
      A Offline
      andre
      wrote on last edited by
      #2

      Some more observations. When I start GammaRay from a terminal, I can see that for most applications, GammaRay just quits as soon as I try to connect. Only for one application (Quassel) it actually seems to do something. I actually do get a UI that I can use. It does seem to make Quassel itself unstable, but at least GammaRay does something with it.

      1 Reply Last reply
      0
      • A Offline
        A Offline
        andre
        wrote on last edited by
        #3

        OK, just an update with some new data (thanks for the help, ZapB!)

        By default, GammaRay builds in release mode. However, GammaRay needs to have the exact same build config as the application you are debugging. As you are debugging, it is likely your application is in debug mode. You can build GammaRay in debug mode by calling the cmake like this, instead of in the way documented in the INSTALL document:
        @
        cmake -G "MinGW Makefiles" -DCMAKE_BUILD_TYPE=debug ..
        @
        The above is for MinGW; you should be able to do the same for MSVC (just add the -DCMAKE... flag).

        It seems that MinGW support is quite new, and in my experience, not quite stable yet. I'll try with MSVC next.

        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