Re: [swift-users] Swift 4.0 LLDBFrontend Crash

Please record this in a bug at bugs.swift.org so that it doesn’t get lost, if you haven’t already. Thanks! Alex Sent from my iPhone  > On 16 Oct 2017, at 19:56, Edward Connell wrote: > > Specifying the clang import location is what is triggering the LLDBFrontend >

Re: [swift-users] Swift 4.0 LLDBFrontend Crash

Specifying the clang import location is what is triggering the LLDBFrontend crash. I think you are saying that I should not need to specify the clang include import location to the compiler. I've attached the unmodified SwiftProtobuf example program found in the docs at

Re: [swift-users] Swift 4.0 LLDBFrontend Crash

> On 16 Oct 2017, at 18:52, Edward Connell wrote: > > While creating a bug report for this problem I placed my simple repro case in > a separate project with default build settings and I found that it no longer > crashes LLDB. > > My main project links to several system C

Re: [swift-users] Swift 4.0 LLDBFrontend Crash

While creating a bug report for this problem I placed my simple repro case in a separate project with default build settings and I found that it no longer crashes LLDB. My main project links to several system C libraries, because I am using libpng, Cuda, etc... In order for LLDB to function with

Re: [swift-users] Swift 4.0 LLDBFrontend Crash

Thanks for the analysis. Can you create a bug at https://bugs.swift.org and attach the reproducing test case? That way it can be routed to the appropriate people, in case they're not on this mailing list. Alex > On 13 Oct 2017, at 22:09, Edward Connell via swift-users

Re: [swift-users] Swift 4.0 LLDBFrontend Crash

I was able to boil down a repro that has nothing to do with my project, woo hoo! Put a break at the print statement and run. When it hits the break point LLDBFrontend crashes. The do/catch seems to be necessary to trigger the crash Swift 4.0 release Ubuntu 16.04 Ed

Re: [swift-users] Swift 4.0 LLDBFrontend Crash

Hi Michael, Thanks, I created and attached a log for you with "types" and "expressions" enabled I set a breakpoint right before calling the function that triggers the crash, enabled logging, then continued. I was trying to reduce the amount of log output to sift through. This was run with the

Re: [swift-users] Swift 4.0 LLDBFrontend Crash

I just added a section to ./docs/DebuggingTheCompiler.rst on how to get enable logging from LLDB. Can you enable the logging there and add file an SR? Michael > On Oct 7, 2017, at 11:27 AM, Edward Connell wrote: > > Hi Michael, > No I am not evaluating an expression or

Re: [swift-users] Swift 4.0 LLDBFrontend Crash

Hi Michael, No I am not evaluating an expression or anything. This all worked fine in past builds. I simply set a breakpoint in a function and after stopping while gathering values for the debugger view, it crashes. It doesn't crash in all functions, but it does crash when trying to stop in many

Re: [swift-users] Swift 4.0 LLDBFrontend Crash

It looks like this is failing during guaranteed optimization. Are you running an expression in the debugger and we are crashing there? Michael > On Oct 6, 2017, at 11:53 AM, Edward Connell via swift-users > wrote: > > While trying to debug a Netlib function, LLDB is

[swift-users] Swift 4.0 LLDBFrontend Crash

While trying to debug a Netlib function, LLDB is crashing I'm not sure what this assert means. *LLDBFrontend: /home/buildnode/jenkins/workspace/oss-swift-4.0-package-linux-ubuntu-16_04/swift/lib/SILOptimizer/Mandatory/AccessEnforcementSelection.cpp:613: (anonymous namespace)::SourceAccess