Fossil SCM

I'm testing the chat feature in a fresh repo initialized with the 2.15 preview version of fossil.

Polling for messages (https://.../chat/chat-poll?before=undefined&n=50:) results in error 400 (Bad Request) due to a segfault:

Segfault (0) fossil() [0x57721a] (1) /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libc.so.6(+0x36b20) [0x7f42bca4eb20] (2) fossil() [0x523ec9] (3) fossil() [0x51c8ad] (4) fossil() [0x579c78] (5) fossil() [0x57b738] (6) fossil() [0x578a13] (7) fossil() [0x40d5b9] (8) /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libc.so.6(__libc_start_main+0xed) [0x7f42bca3aa6d] (9) fossil() [0x40d5ea]

panic: Segfault (0) fossil() [0x57721a] (1) /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libc.so.6(+0x36b20) [0x7f42bca4eb20] (2) fossil() [0x523ec9] (3) fossil() [0x51c8ad] (4) fossil() [0x579c78] (5) fossil() [0x57b738] (6) fossil() [0x578a13] (7) fossil() [0x40d5b9] (8) /gnu/store/fa6wj5bxkj5ll1d7292a70knmyl7a0cr-glibc-2.31/lib/libc.so.6(__libc_start_main+0xed) [0x7f42bc (9) fossil() [0x40d5ea]

i've walked through this code looking for an obvious culprit and am not seeing one. The OP did not say what platform they are on but, based solely on the stack trace, it's presumably is a Mac or BSD, so we may need one of those to reproduce/localize this.

Unable to reproduce the problem. No details provided. The stack trace has no symbols. We have no information with which to pursue this.

I've tried running /chat from a fresh repository using valgrind. No problems were detected.

FWIW, this is on Linux 4.19.0-13-amd64.

@jboy: "Linux 4.19.0-13-amd64" does not tell us anything about the operating system except for its kernel, and there are probably 20+ different operating systems running the Linux 4.x kernel. The system library path seen in your stacktrace (/gnu/...) is not used by any Linux-based OS i'm familiar with.

The hex addresses in the stack trace don't tell us anything we can use. If you are able to build a copy locally and configure it with:

./configure --fossil-debug

the stack trace would be much more informative, giving us source file names and line numbers. If you can get that, and tell us exactly which OS (not kernel) version, compiler version, and fossil version you're using, we might be able to track this down.

As it stands, though, we've been using /chat literally non-stop since December on various servers and have yet to see this problem.

OK, I'll try to do that. Sorry, it wasn't obvious to me what information would help you debug this.

The /gnu folder hierarchy comes from GNU Guix by the way, which I'm using to package Fossil on a Debian system.