Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. Getting crash report from freezed program

Getting crash report from freezed program

Scheduled Pinned Locked Moved C / C++ / MFC
helptutorialquestion
2 Posts 2 Posters 0 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.
  • R Offline
    R Offline
    rrrado
    wrote on last edited by
    #1

    I'm using custom handler for unhandled exception to generate crash dump file in my application (using XCrashReport). The problem is that it does not handle crash when progeram is freezed and user closes it using task manager. Is there a way how to run my exception handler in this case? It is difficult to explain users when they will find drwatson's crash results (and I think it is different in different windows versions). Thank you.


    rrrado

    J 1 Reply Last reply
    0
    • R rrrado

      I'm using custom handler for unhandled exception to generate crash dump file in my application (using XCrashReport). The problem is that it does not handle crash when progeram is freezed and user closes it using task manager. Is there a way how to run my exception handler in this case? It is difficult to explain users when they will find drwatson's crash results (and I think it is different in different windows versions). Thank you.


      rrrado

      J Offline
      J Offline
      James R Twine
      wrote on last edited by
      #2

      I do not think that an application can trap being terminated by Task Manager - too much potential for abuse there, IMHO.    One thing you can try is to create your own watchdog.  Create a separate thread whoses sole purpose in life is to send a message (like WM_NULL) to the main message pump every 10 seconds or so using SendMessageTimeout(...) with an approporiate timeout.    If the timeout expires, intentionally crash the application by doing something like dereferencing a NULL.  Maybe that will cause the SEH handler to fire and give you more information about the state of the application?    Peace!

      -=- James
      Please rate this message - let me know if I helped or not! * * * If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
      Remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
      See DeleteFXPFiles

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups