# MacOS stack traces use the already mmapped executable · gitcafe/zig

[View on GitCafe](https://git.cafe/gitcafe/zig/commit/5c1ec20c9a5c788af9f3402b9a065389eb818e76)

Repository: [gitcafe/zig](https://git.cafe/gitcafe/zig)

Visibility: public

Requested revision: 5c1ec20c9a5c788af9f3402b9a065389eb818e76

Requested commit: 5c1ec20c9a5c788af9f3402b9a065389eb818e76

Commit: 5c1ec20c9a5c788af9f3402b9a065389eb818e76

Tree: d51908c173a8e6201fca9c0acf88aed5f9b15e7a

Author: Andrew Kelley

Committer: Andrew Kelley

## Message

```
MacOS stack traces use the already mmapped executable

...rather than trying to find the executable on the file system.

Also use a more robust PIE offset calculation based on the
available metadata.

And for the last function, use the data that tells the end
rather than assuming 4K.

Also they print in a consistent way with Linux stack traces.

```

## Parents

- [8f96553be81829f1290213d8657d9bc61394b1f7](https://git.cafe/gitcafe/zig/commit/8f96553be81829f1290213d8657d9bc61394b1f7?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zig/tree/5c1ec20c9a5c788af9f3402b9a065389eb818e76?format=markdown)