- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message389312
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | ggardet |
|---|---|
| Recipients | ggardet |
| Date | 2021-03-22.13:29:46 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1616419787.13.0.506382582675.issue43593@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
When Memory Tagging Extension (MTE) [0] is enabled on aarch64, python malloc make programs to crash. I noticed it while trying to use GDB with MTE enabled in user-space [1], and gdb crashed on start-up. Rebuilding python (3.8) using '--without-pymalloc' option allows to workaround the problem. For glibc, you need version 2.33 or later and build glibc with '--enable-memory-tagging' option. I guess that patches similar to glibc's patches are required for pymalloc. [0]: https://community.arm.com/developer/ip-products/processors/b/processors-ip-blog/posts/enhancing-memory-safety [1]: https://en.opensuse.org/ARM_architecture_support#User-space_support |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2021-03-22 13:29:47 | ggardet | set | recipients: + ggardet |
| 2021-03-22 13:29:47 | ggardet | set | messageid: <1616419787.13.0.506382582675.issue43593@roundup.psfhosted.org> |
| 2021-03-22 13:29:47 | ggardet | link | issue43593 messages |
| 2021-03-22 13:29:46 | ggardet | create | |

