# seL4\_GetIPCBuffer causing Cap Fault

**URL:** <https://sel4.discourse.group/t/sel4-getipcbuffer-causing-cap-fault/551>\
**Category:** seL4 kernel\
**Tags:** arm\
**Created:** [July 28, 2022, 7:19am UTC](https://sel4.discourse.group/t/sel4-getipcbuffer-causing-cap-fault/551 "2022-07-28T07:19:56Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![gerwin.klein](https://yyz2.discourse-cdn.com/free1/user_avatar/sel4.discourse.group/gerwin.klein/32/46_2.png) [@gerwin.klein](https://sel4.discourse.group/u/gerwin.klein)\
**Post date:** [July 28, 2022, 10:04am UTC](https://sel4.discourse.group/t/sel4-getipcbuffer-causing-cap-fault/551/6 "2022-07-28T10:04:29Z")

</div>

You might have seen that already, but if your’e interested in Rust on seL4, I should point out that there is a current discussion on what we can/should do to support that from the seL4 foundation perspective [over here](https://sel4.discourse.group/t/pre-rfc-to-effortlessly-develop-sel4-systems-in-rust/539/47).

---

_[View the full topic](https://sel4.discourse.group/t/sel4-getipcbuffer-causing-cap-fault/551)._