# 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:** 13

<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: [August 14, 2022, 12:01am UTC](https://sel4.discourse.group/t/sel4-getipcbuffer-causing-cap-fault/551/13 "2022-08-14T00:01:10Z")

</div>

No worries!

> [@chunky125](#):
>
> One question - is there any reason why selfe-sys would regenerate the bindings to libsel4 at compile time (other than x86 vs aarch64 vs aarch32 vs x86\_64) given that libsel4’s C API should be fixed?

Main reason is that the C API makes use of a lot of conditional compilation options for different seL4 build configurations that don’t map nicely to Rust, i.e. there is not one fixed C API. The discussion in [this thread](https://sel4.discourse.group/t/pre-rfc-to-effortlessly-develop-sel4-systems-in-rust/539) has more details on that and what the plan is to make this a bit less painful in Rust.

(The C API is itself also generated, but that is not the real reason)

---

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