search

AllStarLink / app_rpt

Refactoring and upgrade of AllStarLink's app_rpt, etc.
4 stars 2 forks source link

app_rpt: Invalid memory access when keying up #264

Closed InterLinked1 closed 6 months ago

InterLinked1 commented 6 months ago 
Thread 1 (Thread 0x7fb31d976700 (LWP 2248300)):
#0  __GI___pthread_mutex_lock (mutex=0xdeaddeaddeaddead) at ../nptl/pthread_mutex_lock.c:67
        type = <optimized out>
        __PRETTY_FUNCTION__ = "__pthread_mutex_lock"
        id = <optimized out>
#1  0x000055ca98a802d8 in __ast_pthread_mutex_lock (filename=0x7fb3233924f6 "app_rpt/rpt_telemetry.c", lineno=990, func=0x7fb3233936f0 <__PRETTY_FUNCTION__.3> "rpt_tele_th>
        res = 0
#2  0x00007fb32337c368 in rpt_tele_thread (this=0x7fb338124950) at app_rpt/rpt_telemetry.c:990

Crash can be triggered by running e.g. rpt fun 2509 *70

Telemetry (rpt_tele) pointers themselves seem to suffer the same issue:

Thread 1 (Thread 0x7f5e836af700 (LWP 2265175)):
#0  remque (elem=0x7f5e980e1e70) at insremque.c:50
        next = 0xfeeddeaddead
        prev = 0xc5
#1  0x00007f5ec66f9454 in tele_link_remove (myrpt=0x7f5ec6733400 <rpt_vars>, t=0x7f5e980e1e70) at app_rpt/rpt_link.c:131
No locals.
#2  0x00007f5ec6717239 in rpt_tele_thread (this=0x7f5e980e1e70) at app_rpt/rpt_telemetry.c:2563