# Seg fault when using event loop with IPC calls

**URL:** <https://mangoh.discourse.group/t/seg-fault-when-using-event-loop-with-ipc-calls/1063>\
**Category:** Uncategorized\
**Created:** [January 5, 2018, 7:45pm UTC](https://mangoh.discourse.group/t/seg-fault-when-using-event-loop-with-ipc-calls/1063 "2018-01-05T19:45:23Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![nick](https://sea2.discourse-cdn.com/flex016/user_avatar/mangoh.discourse.group/nick/32/1380_2.png) [@nick](https://mangoh.discourse.group/u/nick)\
**Post date:** [January 8, 2018, 7:52pm UTC](https://mangoh.discourse.group/t/seg-fault-when-using-event-loop-with-ipc-calls/1063/3 "2018-01-08T19:52:20Z")

</div>

Hey @dfrey,

Thanks for the suggestions. Turns out it’s related to something I was curious about in my [last post](http://mangoh.discourse.group/t/ipc-app-failing-to-build/1053/2).

Over the weekend I realized I was writing into an array without specifying the max size in the `.api` file. I added the max size specification and then received a compile time error for conflicting function definitions. I dug into the generated build files a bit and noticed the build system was automatically adding parameters for pointers to array sizes directly after each array pointer. After re-defining my functions to include these new pointers, everything seems to work as expected.

I must say, there was a decent amount to unravel here that wasn’t very obvious by reading the docs or sample apps (unless I missed something). Are the docs open sourced anywhere? I would be happy to spend sometime improving them. Additionally, I could open a pull request to include our example app in the MangOH repo if this is desirable.

Thanks again for the quick help!

---

_[View the full topic](https://mangoh.discourse.group/t/seg-fault-when-using-event-loop-with-ipc-calls/1063)._