On Thu, Jun 07, 2012 at 12:46:07PM +0200, Lluís Batlle i Rossell wrote: > On Thu, Jun 07, 2012 at 06:36:23AM -0400, Richard Hipp wrote: > > On Thu, Jun 7, 2012 at 3:51 AM, Christopher Vance <cjsva...@gmail.com>wrote: > > > > > Firefox gave the message I quoted. > > > Chrome said that the server returned no data. > > > Safari just shows an empty page. > > > Telnet to the relevant port returns no data. > > > > > > > Ok. Good clue. > > > > It appears that the Fossil binary is segfaulting while it is trying to > > generate the page. What version of Fossil are you running? Have you tried > > updating to the tip of trunk? > > As of debugging this, you (Christopher) can look at the PID of the fossil > server, attach to it with gdb (gdb fossil PID), then run "set follow-fork-mode > child", and tell gdb "contiue". Then try to visit the page, and gdb should > stop > at the segfaulting point. > > It would be better if you can do that with the trunk fossil, built with debug > info, without optimisations, and having the source code available.
Another easier way is to activate core dumps. "ulimit -S -c unlimited" before starting the server. Then visit the page, and wait for a core dump file to appear. Then you can load it in gdb: gdb fossil core _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
