Help identify code that break on HardenedBSD
I will do actual debugging of C code, as I believe that's where the error is, but I need help with narrowing it down. When I run gajim on HardenedBSD, Python breaks and creates the core dump. This is was the backtrace:
lldb /usr/local/bin/python3.6 -c python3.6.core (lldb) target create "/usr/local/bin/python3.6" --core "python3.6.core" Core file '/usr/home/meka/python3.6.core' (x86_64) was loaded. (lldb) bt * thread #1, name = 'python3.6', stop reason = signal SIGSEGV * frame #0: 0x0000029cb8eab290 libc.so.7`__res_ndestroy [inlined] __res_nclose(statp=<unavailable>) at res_init.c:818 frame #1: 0x0000029cb8eab25a libc.so.7`__res_ndestroy(statp=0x00007c548b466ce0) at res_init.c:827 frame #2: 0x0000029cb8eaa260 libc.so.7`__res_vinit(statp=0x00007c548b466ce0, preinit=0) at res_init.c:192 frame #3: 0x0000029cbb11d664 libgio-2.0.so.0`do_lookup_records(task=0x0000029cbffed930, source_object=0x0000029cbb948dd0, task_data=0x0000029cbde48400, cancellable=0x0000000000000000) at gthreadedresolver.c:839 (lldb)
As there are 4 other threads, I'm not sure I'm right about the trace and the cause of SIGSEGV, so I'd like to narrow it down by having some small Python code that causes it to break. As libgio function that breaks is do_lookup_records, I just imagine I need the part poking DNS.
Any pointers on where I should look at (Python code only) is appreciated!
PS. The reason I'm asking here is because gajim is the only program that crashes Python like this. Please, help!