ZNC segfaults when compiled with Clang #823

Closed
opened 2026-10-05 04:46:38 +02:00 by adam · 4 comments
Owner

I compiled a fresh (removed all previous build files) copy of ZNC with Clang, and when I go to run it, it segfaults.
If debugging is enabled at build time, everything runs fine

$ uname -a
Linux prestige 4.13.0-37-generic #42-Ubuntu SMP Wed Mar 7 14:13:23 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ clang --version
clang version 4.0.1-6 (tags/RELEASE_401/final)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
$ znc --version
ZNC 1.7.x-git-930-d6bfe504 - https://znc.in
IPv6: yes, SSL: yes, DNS: threads, charset: yes, i18n: no, build: autoconf
I compiled a fresh (removed all previous build files) copy of ZNC with Clang, and when I go to run it, it segfaults. If debugging is enabled at build time, everything runs fine ``` $ uname -a Linux prestige 4.13.0-37-generic #42-Ubuntu SMP Wed Mar 7 14:13:23 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ clang --version clang version 4.0.1-6 (tags/RELEASE_401/final) Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/bin $ znc --version ZNC 1.7.x-git-930-d6bfe504 - https://znc.in IPv6: yes, SSL: yes, DNS: threads, charset: yes, i18n: no, build: autoconf ``` <!-- github-sync-id:311279206 -->
adam closed this issue 2026-10-05 04:46:38 +02:00
Author
Owner

Well.... backtrace from gdb? Some information collected via valgrind? An error message? Anything more than "it crashes"?

Well.... backtrace from `gdb`? Some information collected via `valgrind`? An error message? Anything more than "it crashes"? <!-- github-comment-id:378643336 -->
Author
Owner

There wasn't any error message at runtime appart from Segmentation Fault: core dumped
I'm currently in the process of doing gdb debugging.

There wasn't any error message at runtime appart from `Segmentation Fault: core dumped` I'm currently in the process of doing `gdb` debugging. <!-- github-comment-id:378645884 -->
Author
Owner

I'm not sure why/how this happened but it stopped happening

I'm not sure why/how this happened but it stopped happening <!-- github-comment-id:378649425 -->
Author
Owner

Reopen when you have the details.
Also note that ZNC has continuous testing set up for both GCC and Clang.

Reopen when you have the details. Also note that ZNC has continuous testing set up for both GCC and Clang. <!-- github-comment-id:378676870 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/znc#823