Client 2.5.25 likes to segfault on Debian Testing

client
1

I’ve compiled the client 2.5.25 on a debian testing.
It segfaults quite a lot. I’m not sure, but I think most of the time when resuming a backup.

Mai 20 11:59:14 rmmBook kernel: PipeFile: stdou[115574]: segfault at 7f8024749305 ip 000055e984493126 sp 00007f87e33ffc80 error 4 in urbackupclientbackend[55e98412b000+3bf000] likely on CPU 0 (core 0, sock>
Mai 20 11:59:14 rmmBook kernel: Code: 00 45 84 e4 0f 85 4a 01 00 00 48 89 fb 49 89 f7 49 89 d5 49 89 ce 48 8d 2d 57 f8 cc ff eb 7e 0f 1f 44 00 00 48 8b 01 48 89 cf <ff> 50 20 48 8b 93 90 00 00 00 48 89 44 >
Mai 20 11:59:16 rmmBook systemd-coredump[116849]: [🡕] Process 12387 (urbackupclientb) of user 0 dumped core.
                                                  
                                                  Module libnss_resolve.so.2 from deb systemd-255.5-1.amd64
                                                  Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2.amd64
                                                  Stack trace of thread 115574:
                                                  #0  0x000055e984493126 _ZN11IScopedLockC4EP6IMutex (urbackupclientbackend + 0x3c0126)
                                                  #1  0x000055e9844d4f59 _ZN12PipeFileBase10fillBufferEv (urbackupclientbackend + 0x401f59)
                                                  #2  0x000055e9844d54c8 _ZN12PipeFileBaseclEv (urbackupclientbackend + 0x4024c8)
                                                  #3  0x000055e9841b31c3 _ZN11CPoolThreadclEv (urbackupclientbackend + 0xe01c3)
                                                  #4  0x000055e984173e3a _Z15thread_helper_fPv (urbackupclientbackend + 0xa0e3a)
                                                  #5  0x00007f87ff4a4dbb n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 (deleted) + 0x89dbb)
                                                  ELF object binary architecture: AMD x86-64
2

ps. I’d have the coredump, if that would help?
I’m not sure if I should just upload that here, or if it would contain authentication or other sensitive information

3

Please make sure to compile it with symbols (should be default, but -g).
Then attach gdb (run gdb, then run attach PID), once it crashes run bt and post the result.

Since you compiled it yourself the core dump will not be usefull.