Skip to content

Add a Crash Handling subsection. #376

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.

Sign up for GitHub

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

Merged
alexandersandberg merged 1 commit into from
Sep 4, 2023
Merged

Add a Crash Handling subsection. #376

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions _posts/2023-08-29-swift-5.9-released.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,6 +82,14 @@ A full list of Swift 5.9's Evolution proposals can be found at the end of this p

<!-- TODO: Add more sections with content? -->

### Crash Handling

On Linux, the Swift runtime will now catch program crashes and Swift runtime errors and display a backtrace on the program's output. The backtracer is out-of-process and includes support for `async` functions.

This feature is also available on macOS, although there it is disabled by default (it can be enabled by setting `SWIFT_BACKTRACE=enable=yes`) and you need to ensure that your program is signed with the `com.apple.security.get-task-allow` entitlement.

A more detailed blog covering this feature will be published soon.
Copy link
Contributor

@tomerd tomerd Sep 5, 2023

Choose a reason for hiding this comment

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

"soon" is a relative term. maybe we can reword this so it is evergreen? alternatively we can drop this line

Copy link
Contributor Author

@al45tair al45tair Sep 6, 2023

Choose a reason for hiding this comment

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

The section immediately below this one said a blog post was coming on the debugger "next week". Given that I don't have any idea how the blog post approval process works or how long it takes, I couldn't very well say that, but I think we should do a post about it (I've written something already).

If "soon" is wrong, maybe "in due course"? Though that sounds rather formal?

Copy link
Contributor

@tomerd tomerd Sep 6, 2023

Choose a reason for hiding this comment

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

I think maybe we just drop this line.

Copy link
Contributor Author

@al45tair al45tair Sep 7, 2023

Choose a reason for hiding this comment

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

OK. I'll raise another PR, since this one got merged.

Copy link
Contributor Author

@al45tair al45tair Sep 7, 2023 •
edited
Loading

Choose a reason for hiding this comment

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

That's #381.


### Debugging

In Swift 5.9, we introduced a couple of new features to [LLDB](https://lldb.llvm.org/) and the Swift compiler aimed at making Swift debugging faster and more reliable.
Expand Down