[LBBS-80] mod_mimeparse: Occasional segfault when running tests
mod_mimeparse can sometimes cause issues when unloaded - excerpted from https://productionresultssa10.blob.core.windows.net/actions-results/7cd4b08a-ca58-4b40-b4ba-4ea682d8a679/workflow-job-run-65a7208f-cf57-588d-2741-f2b7d172a85e/logs/job/job-logs.txt?rsct=text%2Fplain&se=2024-11-14T14%3A31%3A16Z&sig=wHEWaz0x4cVIY8JM943MLGm4m1%2FAs1P%2F7SDnOwv5ekY%3D&ske=2024-11-14T23%3A27%3A32Z&skoid=ca7593d4-ee42-46cd-af88-8b886a2f84eb&sks=b&skt=2024-11-14T11%3A27%3A32Z&sktid=398a6654-997b-47e9-b12b-9515b896b4de&skv=2024-08-04&sp=r&spr=https&sr=b&st=2024-11-14T14%3A21%3A11Z&sv=2024-08-04
2024-11-14T14:19:12.8512632Z [2024-11-14 14:19:12.851] [1;32m DEBUG[0m[37137]: [1;37mmodule.c:1600 unload_modules_helper[0m: Attempting to unload mod_mimeparse.so
2024-11-14T14:19:12.8552465Z [2024-11-14 14:19:12.854] [1;32m DEBUG[0m[37137]: [1;37mmodule.c:1612 unload_modules_helper[0m: Module mod_mimeparse.so previously was in use but unloaded on pass 2
2024-11-14T14:19:12.8556317Z [2024-11-14 14:19:12.855] [1;32m DEBUG[0m[37137]: [1;37mmodule.c:310 logged_dlclose[0m: dlclose: mod_mimeparse
2024-11-14T14:19:12.8558167Z [2024-11-14 14:19:12.855] === Unregistering module mod_mimeparse
2024-11-14T14:19:13.3338175Z [2024-11-14 14:19:13.333] [1;32m DEBUG[0m: test.c:886 run_test: Child process 37137 has exited
2024-11-14T14:19:13.3340530Z [2024-11-14 14:19:13.333] [1;31m ERROR[0m: test.c:889 run_test: Process 37137 (/home/runner/work/lbbs/lbbs/tests/test_imap.so) killed, signal Segmentation fault
2024-11-14T14:19:13.3342684Z [2024-11-14 14:19:13.333] [1;32m DEBUG[0m: test.c:895 run_test: Test return code so far is 0
2024-11-14T14:19:13.3344162Z [2024-11-14 14:19:13.333] [1;32m DEBUG[0m: test.c:396 io_relay: read returned 0
2024-11-14T14:19:13.3345250Z ==37137== Memcheck, a memory error detector
2024-11-14T14:19:13.3346169Z ==37137== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
2024-11-14T14:19:13.3347320Z ==37137== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info
2024-11-14T14:19:13.3348647Z ==37137== Command: /usr/sbin/lbbs -b -c -C /tmp/test_lbbs/etc -g -vvvvvvvvv -v -v -dddddddddd
2024-11-14T14:19:13.3349560Z ==37137== Parent PID: 36673
2024-11-14T14:19:13.3350013Z ==37137==
2024-11-14T14:19:13.3350362Z ==37137== Thread 3:
2024-11-14T14:19:13.3350930Z ==37137== Jump to the invalid address stated on the next line
2024-11-14T14:19:13.3351770Z ==37137== at 0x621D683: ???
2024-11-14T14:19:13.3352306Z ==37137== by 0x158F01: thread_run (thread.c:411)
2024-11-14T14:19:13.3353167Z ==37137== by 0x50FBA93: start_thread (pthread_create.c:447)
2024-11-14T14:19:13.3353896Z ==37137== by 0x5188A33: clone (clone.S:100)
2024-11-14T14:19:13.3354785Z ==37137== Address 0x621d683 is in the Text segment of /usr/lib/lbbs/modules/net_smtp.so
2024-11-14T14:19:13.3355642Z ==37137== at 0x621D683: ???
2024-11-14T14:19:13.3356094Z ==37137==
2024-11-14T14:19:13.3356418Z ==37137==
2024-11-14T14:19:13.3357115Z ==37137== Process terminating with default action of signal 11 (SIGSEGV): dumping core
2024-11-14T14:19:13.3358207Z ==37137== Access not within mapped region at address 0x621D683
2024-11-14T14:19:13.3358891Z ==37137== at 0x621D683: ???
2024-11-14T14:19:13.3359427Z ==37137== by 0x158F01: thread_run (thread.c:411)
2024-11-14T14:19:13.3360171Z ==37137== by 0x50FBA93: start_thread (pthread_create.c:447)
2024-11-14T14:19:13.3361126Z ==37137== by 0x5188A33: clone (clone.S:100)
2024-11-14T14:19:13.3361926Z ==37137== If you believe this happened as a result of a stack
2024-11-14T14:19:13.3362891Z ==37137== overflow in your program's main thread (unlikely but
2024-11-14T14:19:13.3363733Z ==37137== possible), you can try to increase the size of the
2024-11-14T14:19:13.3364648Z ==37137== main thread stack using the --main-stacksize= flag.
2024-11-14T14:19:13.3365507Z ==37137== The main thread stack size used in this run was 8388608.Comments
You must be