Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Access violation exception
Forum Updated to NodeBB v4.3 + New Features

Access violation exception

Scheduled Pinned Locked Moved General and Desktop
4 Posts 3 Posters 1.6k 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.
  • N Offline
    N Offline
    noele1995
    wrote on last edited by
    #1

    Hey guys, i was testing my program and i saw that sometimes it crashes with a access violation exception, but qt dosent tell me where it happens and windows only gives me this information. Is there any way to know where it can be happening?

    @ Problem Event Name: APPCRASH
    Application Name: cliente1.exe
    Application Version: 0.0.0.0
    Application Timestamp: 5215121b
    Fault Module Name: cliente1.exe
    Fault Module Version: 0.0.0.0
    Fault Module Timestamp: 5215121b
    Exception Code: c0000005
    Exception Offset: 00002299
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 3082
    Additional Information 1: 0a9e
    Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
    Additional Information 3: 0a9e
    Additional Information 4: 0a9e372d3b4ad19135b953a78882e789@

    1 Reply Last reply
    0
    • SGaistS Offline
      SGaistS Offline
      SGaist
      Lifetime Qt Champion
      wrote on last edited by
      #2

      Hi and welcome to devnet,

      Did you try running your program with a debugger ?

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      1 Reply Last reply
      0
      • N Offline
        N Offline
        noele1995
        wrote on last edited by
        #3

        I dont really know to use a debugger but when i tried it (before posting) it said Qt5Core.dll or something like that not found.

        1 Reply Last reply
        0
        • M Offline
          M Offline
          MuldeR
          wrote on last edited by
          #4

          You better familiarize yourself with debuggers. Without a debugger, it will be very hard - if not impossible - to trace a crash back to the source.

          First of all, you need to make a "debug" build (i.e., a binary with debugging symbols) of your application. And you need to link it against the "debug" version of Qt. Normal "release" binaries won't give you helpful stack trace...

          Once you have a proper debug build, run it "inside" the debugger. As soon as the application crashes, the debugger should trigger a break and show you where (in the source code) it crashed, including a complete callstack of the thread that has crashed. Then you can check the specific code in detail.

          My OpenSource software at: http://muldersoft.com/

          Qt v4.8.6 MSVC 2013, static/shared: http://goo.gl/BXqhrS

          Go visit the coop: http://youtu.be/Jay...

          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