Re: [fossil-users] fossil crash cloning current tcl repository with fossil 2.5 with CentOS 6.5 64 bit
Am 03.05.2018 um 17:37 schrieb Richard Hipp: > On 5/3/18, Harald Oehlmann <harald.oehlm...@elmicron.de> wrote: >> Dear fossil team, >> >> sorry, I have an issue. >> >> fossil 2.5 (binary from the download web site) 64 bit on CentOS 6.5 >> crashes for me as follows when cloning tcl (password replaced by "***"): > > That problem has been fixed on trunk since 2018-03-07. > (https://www.fossil-scm.org/fossil/timeline?c=323299cb=7=ci). I > suppose I need to do a new release to get that fix into > circulation > > Meanwhile, you can download the latest trunk sources from Fossil > (https://fossil-scm.org/fossil/tarball/trunk/fossil.tar.gz) and type > "./configure; make" to get a version of Fossil that works on the Tcl > repository. > Thanks Richard, light-speed answer, that worked. pull the old repository resulted in: Pull from http://oeh...@core.tcl.tk/tcl SQLITE_CORRUPT: database corruption at line 63848 of [9fd0faf517] SQLITE_CORRUPT: statement aborts at 5: [SELECT uuid FROM phantom CROSS JOIN blob USING(rid) /*scan*/ WHERE NOT EXISTS(SELECT 1 FROM shun WHERE uuid=blob.uuid)AND NOT EXISTS(SELECT 1 FROM private WHERE rid=blob.rid)] datab fossil: SQL error: database disk image is malformed but a new clone succeeded. Sergey had another issue on the tcl-core list. He might show-up here and ask for help. A new version would be appreciated if the bug I hit might hit a wider public. Thank you, Harald ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] fossil crash cloning current tcl repository with fossil 2.5 with CentOS 6.5 64 bit
Dear fossil team, sorry, I have an issue. fossil 2.5 (binary from the download web site) 64 bit on CentOS 6.5 crashes for me as follows when cloning tcl (password replaced by "***"): $ fossil clone http://oehhar:***@core.tcl.tk/tcl tcl.fossil remember password (Y/n)? Y Round-trips: 143 Artifacts sent: 0 received: 161289 Clone done, sent: 45913 received: 148242259 ip: 74.208.161.176 Rebuilding repository meta-data... *** buffer overflow detected ***: fossil terminated === Backtrace: = [0x730e81] [0x77a212] [0x77a18e] [0x4e31dc] [0x4d1c39] [0x458082] [0x46ad91] [0x41e147] [0x405ca2] [0x716056] [0x71624a] [0x4062f9] === Memory map: 0040-009e9000 r-xp fd:00 144966 /usr/local/bin/fossil 00be8000-00c02000 rw-p 005e8000 fd:00 144966 /usr/local/bin/fossil 00c02000-00c0c000 rw-p 00:00 0 02597000-060be000 rw-p 00:00 0 [heap] 3ac580-3ac582 r-xp fd:00 133643 /lib64/ld-2.12.so 3ac582-3ac5a2 ---p 0002 fd:00 133643 /lib64/ld-2.12.so 3ac5a2-3ac5a21000 r--p 0002 fd:00 133643 /lib64/ld-2.12.so 3ac5a21000-3ac5a22000 rw-p 00021000 fd:00 133643 /lib64/ld-2.12.so 3ac5a22000-3ac5a23000 rw-p 00:00 0 3ac5c0-3ac5d8a000 r-xp fd:00 133796 /lib64/libc-2.12.so 3ac5d8a000-3ac5f8a000 ---p 0018a000 fd:00 133796 /lib64/libc-2.12.so 3ac5f8a000-3ac5f8e000 r--p 0018a000 fd:00 133796 /lib64/libc-2.12.so 3ac5f8e000-3ac5f9 rw-p 0018e000 fd:00 133796 /lib64/libc-2.12.so 3ac5f9-3ac5f94000 rw-p 00:00 0 3ac800-3ac8016000 r-xp fd:00 156389 /lib64/libresolv-2.12.so 3ac8016000-3ac8216000 ---p 00016000 fd:00 156389 /lib64/libresolv-2.12.so 3ac8216000-3ac8217000 r--p 00016000 fd:00 156389 /lib64/libresolv-2.12.so 3ac8217000-3ac8218000 rw-p 00017000 fd:00 156389 /lib64/libresolv-2.12.so 3ac8218000-3ac821a000 rw-p 00:00 0 7f490390f000-7f490391 rw-p 00:00 0 7f490391-7f4903915000 r-xp fd:00 151078 /lib64/libnss_dns-2.12.so 7f4903915000-7f4903b14000 ---p 5000 fd:00 151078 /lib64/libnss_dns-2.12.so 7f4903b14000-7f4903b15000 r--p 4000 fd:00 151078 /lib64/libnss_dns-2.12.so 7f4903b15000-7f4903b16000 rw-p 5000 fd:00 151078 /lib64/libnss_dns-2.12.so 7f4903b16000-7f4903c16000 rw-p 00:00 0 7f4903c16000-7f4903c23000 r-xp fd:00 151248 /lib64/libnss_files-2.12.so 7f4903c23000-7f4903e22000 ---p d000 fd:00 151248 /lib64/libnss_files-2.12.so 7f4903e22000-7f4903e23000 r--p c000 fd:00 151248 /lib64/libnss_files-2.12.so 7f4903e23000-7f4903e24000 rw-p d000 fd:00 151248 /lib64/libnss_files-2.12.so 7ffc32505000-7ffc3251a000 rw-p 00:00 0 [stack] 7ffc32526000-7ffc32527000 r-xp 00:00 0 [vdso] ff60-ff601000 r-xp 00:00 0 [vsyscall] Abgebrochen (The last word "Abgebrochen" is German for "Aborted") The same happens with "fossil sync". This only happens for the tcl repository. Tk, tcllib etc. do not crash. Do you see the same issue ? Thanks, Harald ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Enhancement: commit and close merged leaf
Am 12.07.2013 10:25, schrieb Jan Nijtmans: Well, just try out the merge-integrate branch. I would say the glass is full again.;-) Congratulation, very impressive ! - Harald ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Enhancement: commit and close merged leaf
Am 11.07.2013 11:07, schrieb Jan Nijtmans: 2013/7/10 Stephan Beal sgb...@googlemail.com: That well surpasses my understanding of how merging is tracked, so i'll just be quiet now ;). Well, merge-tracking is a part of fossil which I understand very well. So I did just a little bit hacking: Jan, you are surprising me again and again ! Looks really helpful and well thought (but I am even more in Stephans position to stay quiet due to big lack of understanding...) Admiration, Harald ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Enhancement: commit and close merged leaf
Following hint by Andreas: https://groups.google.com/forum/#!topic/comp.lang.tcl/JwSNrTYgjTk the following enhancement to fossil is proposed: with fossil commit, there should be a possibility (parameter) to close a merged branch. So here is a current typical session to merge a branch to trunk: 1) fossil open repo 2) fossil merge branch 3) fossil commit 4) And then, I go to the web interface and set the closed leaf property of the branch. The last step would be natural for me to de done with the fossil commit. Thank you, Harald ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Enhancement: commit and close merged leaf
Am 10.07.2013 11:51, schrieb Stephan Beal: On Wed, Jul 10, 2013 at 9:37 AM, Harald Oehlmann harald.oehlm...@elmicron.de mailto:harald.oehlm...@elmicron.de wrote: 1) fossil open repo 2) fossil merge branch 3) fossil commit 4) And then, I go to the web interface and set the closed leaf property of the branch. The last step would be natural for me to de done with the fossil commit. Might it not make more sense for fossil to close the leaf when merging? If it waits until commit then it has to remember and arbitrary number of leaves for arbitrarily long (timespan between merge and commit) and then close them all as part of the commit. The number of potential error cases during the commit then explodes. Closing at merging is also not ideal because it often happens that a merge gets tossed out in the process of trying to fix conflicts (very often i have non-trivial merge conflicts i end up tossing out the merge and starting over from a different angle). Very good idea ! It is ok to also initiate it with the fossil merge and do it with fossil commit. The fact to specify it with fossil merge has two advantages: - the closed branch tag is directly in the command, which is clearer - multiple merges may be closed or not by one commit. I personally would be glad, if I could already manage a single merge... -Harald ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
