On Aug 6, 2018, at 11:30 AM, Philip Bennefall <phi...@blastbay.com> wrote:
> a second commit right afterwards caused a segfault again

In advance of drh getting time to work on this, maybe you could give two 
debugging steps on your end:

1. If you’re doing this on a platform that will run Valgrind, try running a 
debug build of Fossil under it against your repository:

    $ cd /path/to/fossil/source/tree
    $ ./configure --fossil-debug
    $ make clean && make && sudo make install
    $ cd /path/to/checkout/directory
    $ valgrind fossil status

2. If you get a vgcore out of that, load it into GDB and produce a backtrace.  
If not, cores are probably disabled there, so run Fossil under gdb and get a 
backtrace that way.

(The first way is more likely to give a clean backtrace, as the failure gets 
caught before it can cause damage.)
fossil-users mailing list

Reply via email to