Unfortunately, my first stab at this failed: (gdb) break repo_list_page Breakpoint 1 at 0x7ccc0: file ./src/main.c, line 1238. (gdb) run http --repolist /fossils <getstuff Starting program: /root/fossil-2.4/fossil http --repolist /fossils <getstuff warning: Error disabling address space randomization: Operation not permitted Could not trace the inferior process. Error: ptrace: Operation not permittedDuring startup program exited with code 127. (gdb)
This was done in the same container which is failing as previously described. The host is running rancheros, which is a very stripped down and highly customized distribution meant specifically for hosting docker containers. As such, I'll have to find a different host and distribution to test this against. Things I have learned thus far: * fossil fails in a similar way when serving a specific repository file. In this case, the web page presents "Not Found" or something similar. * fossil appears to work properly on this mountpoint when not serving; i can open one of the repository files, edit, commit, sync back across the network, etc. * fossil does serve both a repo file and a directory if these files are copied to a different local directory. The filesystem mount looks like this: ranch2@10.1.51.120:fossils on /fossils type fuse.sshfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0) So ... I'll continue by attempting the same type of thing on a different and more complete distribution, outside of a container, so that gdb will work if fossil fails there as well. But hopefully someone will spot something in the information above and share an "ah-hah" moment. Thanks for your assistance thus far. ----- On Dec 20, 2017, at 8:35 PM, Richard Hipp d...@sqlite.org wrote: > On 12/20/17, dewey.hyl...@gmail.com <dewey.hyl...@gmail.com> wrote: >> Would someone help me understand what I'm seeing here? I expect a list of >> repositories >> in the web page output, but am told there are none. > > I don't understand it either. > > To debug, recompile Fossil with -g and -O0. Create a HTTP request > text file like this: > > GET / HTTP/1.0\n > \n > > (The first line is "GET /" and the second line is blank. The \r > characters normally required by HTTP are optional.) Then run fossil in > gdb. Set a breakpoint on the routine repo_list_page and run this > command: > > run http --repolist /fossils <r1.txt > > Single step through the repolist routine and try to figure out why it > is not finding your repository files. Please let us know what you > discover. > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
