<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi<div class=""><br class=""></div><div class="">Here’s the directory although these are all old and not related to the crash under discussion (the most recent crash is for swiftc 800.0.63, the Xcode 3.1 toolchain appears to be 802.0.48). I was able to reproduce today with Xcode 8.3.1 update but no log with today’s date. </div><div class=""><br class=""></div><div class="">I’ll file a bug report, if anything else you think worth my trying to help understand cause let me know. I’ve build Swift toolchain from source in the past so could try setting up with debug version etc. to see if that gets any further info. </div><div class=""><br class=""></div><div class="">Mark<br class=""><div class=""><br class=""></div><span class=""><font face="Monaco" class="">$ ls ~/Library/Logs/DiagnosticReports/swift*.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-18-114620_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-18-134122_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-18-134156_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-18-134450_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-18-173731_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-19-075327_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-19-081344_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-19-090802_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-19-090921_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-19-094003_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-19-094027_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-19-095907_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-19-201252_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-19-201726_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-20-065123_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-20-065148_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-20-065323_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-20-070358_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-20-103428_MacBook-Pro-5.crash<br class="">/Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-24-075534_MacBook-Pro-5.crash<br class=""></font><br class=""><blockquote type="cite" class="">On 7 Apr 2017, at 12:00, Johannes Weiß <<a href="mailto:johannesweiss@apple.com" class="">johannesweiss@apple.com</a>> wrote:<br class=""><br class="">Hi Mark,<br class=""><br class="">That's unfortunate. Assuming you're on macOS, do you mind running<br class=""><br class="">ls ~/Library/Logs/DiagnosticReports/swift*.crash<br class=""><br class="">that might reveal some compiler crash reports. If yes I think the best would be to file a bug for these crashes on <a href="http://bugs.swift.org" class="">http://bugs.swift.org</a> . What presumably would be most helpful is a small reproduction of that crash but I realise that can be hard at times...<br class=""><br class="">Thanks,<br class=""> Johannes<br class=""><br class=""><br class=""><blockquote type="cite" class="">On 7 Apr 2017, at 07:31, Mark Woollard via swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>> wrote:<br class=""><br class="">Following upgrade to Xcode 8.3 / Swift 3.1 I have a project where the compiler is crashing when Swift optimisation is enabled in release builds (whole module or single file). Project builds fine for earlier compiler releases. The crash gives no stack trace in console. The crash occurs for one framework component within a complex project with multiple frameworks + app with lots of inter-dependency so its hard to know what specifically is causing the issue or produce something to reproduce and file with a bug report. If I turn off optimisation for that one framework the whole project builds.<br class=""><br class="">I gather crashes related to optimisation have been seen by others from discussions I’ve seen elsewhere ?<br class="">What is the status of the issue, ETA for a fix ?<br class="">Is there anything I can do to help provide info to fix the issue ? I might be able to build debug version of compiler and try and use it under debugger with the project for example, or is there anything else I can do to get you useful info ?<br class=""><br class="">Thanks<br class="">Mark<br class="">_______________________________________________<br class="">swift-dev mailing list<br class=""><a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-dev<br class=""></blockquote><br class=""></blockquote><br class=""></span></div></body></html>