# Tracing a segfault

**URL:** <https://community.allstarlink.org/t/tracing-a-segfault/19519>\
**Category:** Archive\
**Created:** [August 12, 2022, 9:56pm UTC](https://community.allstarlink.org/t/tracing-a-segfault/19519 "2022-08-12T21:56:33Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![K9WKJ](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/a8b319/32.png) [@K9WKJ](https://community.allstarlink.org/u/K9WKJ)\
**Post date:** [August 12, 2022, 10:32pm UTC](https://community.allstarlink.org/t/tracing-a-segfault/19519/3 "2022-08-12T22:32:39Z")

</div>

I see this has been noted before early last year

> <https://github.com/AllStarLink/ASL-Asterisk/issues/5>
>
> The following message is logged once every 30 seconds for each status reporting …node: 
> 
> \`segfault at c8 ip 00007ff47a27a118 sp 00007ff4783f12a0 error 4 in app\_rpt.so\[7ff47a26d000+39000\]\`
> 
> App\_rpt does not crash. Status Page updates appear normal. 
> 
> Temporary work around is to comment each rpt.conf occurrence of \`statpost\_url=http://stats.allstarlink.org/uhandler.php ; Status updates\`.

and someone was poking at the code  
and looked like there was a commit or at least a request  
is this not rolled up in the current distribution?  
can I just scab the new app\_rpt.so in or will it want a recompile  
ugggg

de k9wkj

---

_[View the full topic](https://community.allstarlink.org/t/tracing-a-segfault/19519)._