Skip to content
New issue

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

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

Already on GitHub? # to your account

Backtrace Support for arm64 #65

Open
grahamburgsma opened this issue Mar 17, 2022 · 5 comments
Open

Backtrace Support for arm64 #65

grahamburgsma opened this issue Mar 17, 2022 · 5 comments

Comments

@grahamburgsma
Copy link

Now that there are official arm docker images, it seems appropriate to also have backtrace support.

The issue here swift-server/swift-backtrace#19 from October 2019 requests support for it, but it doesn't look like there has been much progress on it.

Is there anything the SSWG can do to push that forward? I've been running a production Vapor app on AWS Graviton and have been missing the backtrace support for a couple of difficult to find crashes.

Thanks!

@Lukasa
Copy link
Contributor

Lukasa commented Mar 18, 2022

I think this is a reasonable thing to ask of the SSWG, yeah.

@0xTim
Copy link
Member

0xTim commented Mar 18, 2022

We'll discuss this and see what we can do

@rnantes
Copy link

rnantes commented Aug 19, 2022

+1 for this feature it is a big pain point for me

@t089
Copy link

t089 commented Sep 19, 2022

Is there some progress?

@tomerd
Copy link
Contributor

tomerd commented Sep 19, 2022

I have not had time to look into this in too many details, but I suspect this is mostly a build issue. libbacktrace should be usable on arm64, but this packages picks and chooses the relevant files from the project and builds them with SwiftPM. if anyone has cycles, the idea would be to figure out what the build setup on arm64 should look like and then update the SwiftPM configuration to include the right files under that architecture

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants