Nothing in the system wide logs (not even a diagnostics directory there) - I’ll wait and see what the West Coast guys have to say :-) Mark
> On 7 Apr 2017, at 12:44, Johannes Weiß <johanneswe...@apple.com> wrote: > > Hi Mark, > > >> 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. > > oh, that's interesting. Just for completeness, maybe it went into the system > wide reports (unlikely): > > ls /Library/Logs/DiagnosticReports/swift*.crash > > ? > > >> 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. > > That sounds like it could prove really helpful. Most of the Swift core devs > are in California so they'll wake up in a couple of hours and might have some > more questions. > > Many thanks, > Johannes > > >> >> >> Mark >> >> $ ls ~/Library/Logs/DiagnosticReports/swift*.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-18-114620_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-18-134122_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-18-134156_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-18-134450_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-18-173731_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-19-075327_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-19-081344_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-19-090802_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-19-090921_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-19-094003_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-19-094027_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-19-095907_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-19-201252_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-19-201726_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-20-065123_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-20-065148_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-20-065323_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-20-070358_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-20-103428_MacBook-Pro-5.crash >> /Users/markw/Library/Logs/DiagnosticReports/swift_2017-03-24-075534_MacBook-Pro-5.crash >> >>> On 7 Apr 2017, at 12:00, Johannes Weiß <johanneswe...@apple.com> wrote: >>> >>> Hi Mark, >>> >>> That's unfortunate. Assuming you're on macOS, do you mind running >>> >>> ls ~/Library/Logs/DiagnosticReports/swift*.crash >>> >>> that might reveal some compiler crash reports. If yes I think the best >>> would be to file a bug for these crashes on http://bugs.swift.org . What >>> presumably would be most helpful is a small reproduction of that crash but >>> I realise that can be hard at times... >>> >>> Thanks, >>> Johannes >>> >>> >>>> On 7 Apr 2017, at 07:31, Mark Woollard via swift-dev <swift-dev@swift.org> >>>> wrote: >>>> >>>> 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. >>>> >>>> I gather crashes related to optimisation have been seen by others from >>>> discussions I’ve seen elsewhere ? >>>> What is the status of the issue, ETA for a fix ? >>>> 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 ? >>>> >>>> Thanks >>>> Mark >>>> _______________________________________________ >>>> swift-dev mailing list >>>> swift-dev@swift.org >>>> https://lists.swift.org/mailman/listinfo/swift-dev >>> >> > _______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
