FYI: the problem got fixed in trunk 2 days ago. https://www.fossil-scm.org/index.html/info/8c22e1bbcd8ec048
-- Martin G. Le lun. 20 mars 2017 à 13:22, Warren Young <war...@etr-usa.com> a écrit : > On Mar 18, 2017, at 11:59 PM, Andy Bradford <amb-fos...@bradfords.org> > wrote: > > > > Thus said "Tony Papadimitriou" on Sat, 18 Mar 2017 01:59:21 +0200: > > > >> The following command crashes fossil (older and up to current > >> version). > > > > It doesn't crash for me. > > It didn’t crash for me initially, either. I initially tried doing it from > outside of a Fossil checkout tree, assuming all that was needed was the > cloned DB file, referred to by -R. Then I cd’d to one of the checkouts for > that repository referred to by -R, and it started happening here. > > The file and line number in my previous email comes from a GDB backtrace > in a core file. “print z” at the crash site says 0. > > > Can you be more specific as to which version? > > This is fossil version 2.1 [f89e0d4a91] 2017-03-10 17:19:19 UTC > > That is, the 2.1 release version. > > > Also, which OS? > > I did this on CentOS 7, but I suspect Tony is on Windows, from past > posts. I do not believe this bug is OS-specific. > _______________________________________________ > 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
