Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Behind the Scenes
  3. Qt.io webservices
  4. Options for Collecting Stack Trace Windows Qt5 Mingw

Options for Collecting Stack Trace Windows Qt5 Mingw

Scheduled Pinned Locked Moved Qt.io webservices
3 Posts 2 Posters 2.4k 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.
  • J Offline
    J Offline
    jaywozz
    wrote on last edited by
    #1

    I have C++ App with a random crash that occurs on release machines that I cannot create at will in debugging environment. I have spent some time reviewing options, but it is not clear what is my best option to pursue. I need a stack trace of my application each time it crashes to see what code we were in when we crashed. How do I deploy the framework for a later review of the crash? This is my first forum and my first question. Thanks.

    1 Reply Last reply
    0
    • S Offline
      S Offline
      steno
      wrote on last edited by
      #2

      For release builds, I like to use App verifier for detecting heap corruptions. You can also generate debug information in release as well.

      1 Reply Last reply
      0
      • J Offline
        J Offline
        jaywozz
        wrote on last edited by
        #3

        We are running on Windows 7

        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