[Issue 11865] Unhandled exception does not show crash dialog
https://issues.dlang.org/show_bug.cgi?id=11865 Iain Buclaw changed: What|Removed |Added Priority|P2 |P3 --
[Issue 11865] Unhandled exception does not show crash dialog
https://issues.dlang.org/show_bug.cgi?id=11865 Andrej Mitrovic andrej.mitrov...@gmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED CC||andrej.mitrov...@gmail.com Resolution|FIXED |--- --- Comment #7 from Andrej Mitrovic andrej.mitrov...@gmail.com --- Wrong commit message closed this, sorry. --
[Issue 11865] Unhandled exception does not show crash dialog
https://issues.dlang.org/show_bug.cgi?id=11865 --- Comment #6 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/D-Programming-Language/dlang.org https://github.com/D-Programming-Language/dlang.org/commit/779142e3332a07ce3bf431befb572bafd5024066 Fix Issue 11865 - Document the package module feature. https://github.com/D-Programming-Language/dlang.org/commit/b0e70804c9afe9a8f5602f51bc1bbce367ac0c45 Merge pull request #551 from AndrejMitrovic/Fix11867 Issue 11865 - Document the package module feature. --
[Issue 11865] Unhandled exception does not show crash dialog
https://d.puremagic.com/issues/show_bug.cgi?id=11865 --- Comment #4 from github-bugzi...@puremagic.com 2014-01-06 00:03:17 PST --- Commits pushed to master at https://github.com/D-Programming-Language/druntime https://github.com/D-Programming-Language/druntime/commit/d251e4fa1f3298b07f2e57acc3c1c6ede48531b8 rt.dmain2: Fix Issue 11865 - Unhandled exception does not show crash dialog If a console window is not present, display uncaught exceptions in a standard Windows message box. https://github.com/D-Programming-Language/druntime/commit/d0494632d6d7789fd4f94994ef52983935123052 Merge pull request #703 from CyberShadow/windows-crash-dialog Fix Issue 11865 - Unhandled exception does not show crash dialog -- Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 11865] Unhandled exception does not show crash dialog
https://d.puremagic.com/issues/show_bug.cgi?id=11865 --- Comment #5 from Vladimir Panteleev thecybersha...@gmail.com 2014-01-06 10:18:46 EET --- (In reply to comment #3) Could there be a way to set a delegate that is called when there is an uncaught exception and have an easy way to get the exception type, name, and stack trace? Yes. In fact, something like that existed in the runtime a while ago. However, you can achieve mostly the same by writing your own WinMain as shown here: http://dlang.org/windows.html This page is a bit outdated. Note the exceptionHandler parameter: this is the mechanism mentioned above that no longer works, and those overloads of Runtime.initialize/terminate are now deprecated. (Martin Nowak removed them in b95be7e55e57a4ff065f1dc5f3362fc476d85f4d. Before that, Walter Bright wrote in a comment: Note that if we get here, the runtime is in an unknown state. I'm not sure what the point of calling dg is.). However, the general idea still works, if you don't care about exceptions thrown during runtime initialization / deinitialization (this includes static constructors/destructors). Just replace the MessageBoxA call with your custom error-handling code. -- Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 11865] Unhandled exception does not show crash dialog
https://d.puremagic.com/issues/show_bug.cgi?id=11865 --- Comment #3 from Jordan Miner jmin...@gmail.com 2014-01-05 18:31:08 PST --- Thanks for writing the patch. Sounds like a good improvement that I'll use during development. Reading about WER more, I think I'd rather bypass it and handle everything myself. Could there be a way to set a delegate that is called when there is an uncaught exception and have an easy way to get the exception type, name, and stack trace? In the delegate, I could start a helper process that reads the information from the crashed process and uploads it (to avoid doing too much in a crashed process). For others who want to use WER, it looks like they could call WerReportCreate() and WerReportSubmit() from the delegate to trigger WER. The default delegate could write the info to the console or show a dialog, depending on whether there is a console. What do you think? -- Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 11865] Unhandled exception does not show crash dialog
https://d.puremagic.com/issues/show_bug.cgi?id=11865 Vladimir Panteleev thecybersha...@gmail.com changed: What|Removed |Added Keywords||pull CC||thecybersha...@gmail.com --- Comment #1 from Vladimir Panteleev thecybersha...@gmail.com 2014-01-05 08:51:42 EET --- https://github.com/D-Programming-Language/druntime/pull/703 With this patch, we'll show the uncaught exception details in a standard Windows message box. These are usually more useful than the standard Windows crash dialog, since they contain the exception type, the exception message, and (if the program was compiled with debug info), a stack trace. Currently it is not possible to disable the D standard top-level exception handler from within the program or via a compiler/linker switch. It is disabled automatically if the program was started under a debugger, though. -- Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 11865] Unhandled exception does not show crash dialog
https://d.puremagic.com/issues/show_bug.cgi?id=11865 --- Comment #2 from Vladimir Panteleev thecybersha...@gmail.com 2014-01-05 09:02:36 EET --- I would want to upload stack traces to my own server instead of Microsoft's So, do I understand correctly that D's standard uncaught exception handler does not apply to your problem, and you need uncaught exceptions to go to WER? If so, would the standard uncaught exception handler being disabled when a variable is present in the environment be an acceptable solution for you? Since you mentioned a custom WER server, you're already using a custom configuration on the users' PCs, so adding an environment variable shouldn't be very different, right? -- Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
