Skip to content

Instead of crashing for bad output-file-map path, exit. Also print the path in the diagnostic. rdar://39660680 #16126

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

davidungar
Copy link
Contributor

Fix a bug in the driver that caused a crash if passed a bad path for -output-file-map. Also add the path to the diagnostic. Add a test.

@davidungar
Copy link
Contributor Author

@swift-ci please smoke test

@davidungar davidungar requested a review from graydon April 24, 2018 05:43
@davidungar
Copy link
Contributor Author

@swift-ci please smoke test

@davidungar davidungar force-pushed the exit-dont-crash-for-missing-output-file-map branch from 2d4179b to 2b89d1c Compare April 24, 2018 18:55
Copy link
Contributor

@graydon graydon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

@davidungar
Copy link
Contributor Author

Tx!

@davidungar davidungar merged commit 37e134c into swiftlang:master Apr 24, 2018
@davidungar davidungar changed the title Instead of crashing for bad output-file-map path, exit. Also print the path in the diagnostic. Instead of crashing for bad output-file-map path, exit. Also print the path in the diagnostic. rdar://39660680 Apr 25, 2018
davidungar pushed a commit to davidungar/swift that referenced this pull request Apr 26, 2018
…r-missing-output-file-map

Instead of crashing for bad output-file-map path, exit. Also print the path in the diagnostic.
@davidungar davidungar deleted the exit-dont-crash-for-missing-output-file-map branch June 14, 2019 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants