Closed DerellLicht closed 5 years ago
Perhaps Windows 10 changed how JIT debuggers are invoked. I'll take a look.
Please confirm which Windows version you have (run winver
)
In the meanwhile, you could try doing
path\to\drmingw\bin\catchsegv.exe name-of-your-program.exe
from the command line, and see whether it catches your program crash or not?
Windows info: Version 1709 (OS Build 16299.611)
Unfortunately, I don't seem to be able to force that program crash any more !! I hate that!! I'll have to generate some other error to test this out...
Okay, I got the error to recur, and your catchsegv program worked beautifully... I initially was not getting symbol information for my app functions, but that was an error in my Makefile. So upshot is, yes, catchsegv.exe works just fine !!! Thank you for your help.
This is a satisfactory solution for me, so if you wish, you can close this ticket. However, if you want to pursue this further and try to get drmingw itself working, I will be happy to do any further analysis that can assist you.
I reproed here.
It works if one installs drmingw with -a
option, that is:
drmingw -i -a
That is, it seems the non-auto mode (that is the WER dialog saying app crash and whether to debug) doesn't work...
Okay, thank you for this info!! I'm make a note of this and re-install at work...
I'm building my application using MinGW V4.4.1; 32-bit application; I build with -g debug flag.
I wanted to use DrMinGW to find out what's going wrong, as I've done so often in the past, but your program doesn't trigger at all when my program crashes, for some reason. I get the dialog for "this program has terminated improperly blah blah blah", but I only get the Close button, no Debug button.
I ran 'drmingw.exe -i' as admin on this machine, and it said that it installed successfully.
Any idea what is going on, and maybe what could be done about it?