[llvm-bugs] [Bug 33854] New: LLVM tools are not playing Visual Studio debugger friendly

via llvm-bugs llvm-bugs at lists.llvm.org
Wed Jul 19 13:54:59 PDT 2017


https://bugs.llvm.org/show_bug.cgi?id=33854

            Bug ID: 33854
           Summary: LLVM tools are not playing Visual Studio debugger
                    friendly
           Product: clang
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: Frontend
          Assignee: unassignedclangbugs at nondot.org
          Reporter: jujjyl at gmail.com
                CC: llvm-bugs at lists.llvm.org

It looks like the various tools in the Clang toolchain are set to internally
capture all crash signals and generate crash minidumps from them. This prevents
from being able to attach a Visual Studio debugger at the time of crash. By
default if applications do not register any signal handlers, the VC runtime
will pop up a debug handler dialog asking to attach a VS debugger in Debug
builds.

Would it be possible to make it so that Debug CMake config build would by
default not attach crash handlers, so that VC runtime would pop up the debugger
dialog? Additionally, it would be good to hook onto an environment variable,
say LLVM_DISABLE_CRASH_HANDLERS=1, which if set, would cause LLVM to hand off
to Visual Studio debugging.

Now I notice I need to do custom builds that comment out the crash handlers,
e.g. for llc.exe, in llc.cpp:

int main(int argc, char **argv) {
//  sys::PrintStackTraceOnErrorSignal(argv[0]);

It would be nice for LLVM to behave debugger friendly out of the box.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20170719/892f4016/attachment.html>


More information about the llvm-bugs mailing list