Re: [fossil-users] ./src/delta.c:231: checksum: Assertion failed

On Feb 19, 2016, at 9:04 PM, Andy Bradford wrote: > > Notice here that my stack has much smaller numbers pTarget=0xcf7c6300 vs > pTarget=0x7fffaf5dccd0: I’m on a 64-bit machine. If yours OS or executable is 32-bit, that explains it. Also, different OSes use different

Re: [fossil-users] ./src/delta.c:231: checksum: Assertion failed

Thus said Stephan Beal on Sat, 20 Feb 2016 04:46:51 +0100: > i see lots of 0x7ffs in there, and i happen to know that > se=... is indeed a stack-allocated object. i'm a bit surprised that > argv is, but not overly so. Yeah, I guess it's more common than I thought and I'm not

Re: [fossil-users] ./src/delta.c:231: checksum: Assertion failed

On Sat, Feb 20, 2016 at 4:42 AM, Andy Bradford wrote: > Thus said Martin Gagnon on Fri, 19 Feb 2016 20:56:47 -0500: > > > This is not usually stack addresses? > > Yes, for allocated memory, but how big is the stack that supports an > address that big? > Dunno.

Re: [fossil-users] ./src/delta.c:231: checksum: Assertion failed

Thus said Martin Gagnon on Fri, 19 Feb 2016 20:56:47 -0500: > This is not usually stack addresses? Yes, for allocated memory, but how big is the stack that supports an address that big? Andy -- TAI64 timestamp: 400056c7e0c0 ___ fossil-users

Re: [fossil-users] ./src/delta.c:231: checksum: Assertion failed

On Sat, Feb 20, 2016 at 2:53 AM, Andy Bradford wrote: > Thus said Warren Young on Fri, 12 Feb 2016 09:45:34 -0700: > > > #5 0x004237f6 in blob_delta_create (pOriginal= out>, pTarget=0x7fffe330, pDelta=0x7fffe370) at ./src/deltacmd.c:40 > > I could be

Re: [fossil-users] ./src/delta.c:231: checksum: Assertion failed

> Le 19 févr. 2016 à 20:53, Andy Bradford a écrit : > > Thus said Warren Young on Fri, 12 Feb 2016 09:45:34 -0700: > >> #5 0x004237f6 in blob_delta_create (pOriginal=> out>, pTarget=0x7fffe330, pDelta=0x7fffe370) at ./src/deltacmd.c:40 > > I could be

Re: [fossil-users] ./src/delta.c:231: checksum: Assertion failed

Thus said Warren Young on Fri, 12 Feb 2016 09:45:34 -0700: > #5 0x004237f6 in blob_delta_create (pOriginal=, > pTarget=0x7fffe330, pDelta=0x7fffe370) at ./src/deltacmd.c:40 I could be wrong, but those seem like extreme memory addresses... Anyone? Andy -- TAI64 timestamp:

Re: [fossil-users] fossil all remove?

On 2/19/2016 4:51 PM, Richard Hipp wrote: On 2/19/16, Warren Young wrote: Again, I think the cleanup should be automatic. But if you are still having trouble the "fossil all ignore DIRECTORY" command should manually remove the offending check-out from the list. Maybe the

Re: [fossil-users] Scripting fossil

On Fri, Feb 19, 2016 at 4:55 PM, Warren Young wrote: > On Feb 18, 2016, at 7:20 PM, Scott Robison > wrote: > > > > As it turns out, this wasn't a great plan. > > I agree. I even dislike checking configure scripts generated by autoconf > and similar

Re: [fossil-users] fossil all remove?

On 2/19/16, Warren Young wrote: > On Feb 19, 2016, at 3:06 AM, Tino Lange > wrote: >> >> How can I get rid of an entry in "fossil all ls -c" for which the >> checkout does not exist anymore? Do I need to fiddle with SQL? > > I think this happens

Re: [fossil-users] repo sharding (was: libfossil scripting mini-demo)

On Sat, Feb 20, 2016 at 12:51 AM, Warren Young wrote: > On Feb 18, 2016, at 8:56 AM, Stephan Beal wrote: > > > > s2> var m = c.loadManifest('current');; > > > > s2> foreach(m=>k) print(k) > > I wonder, would it be practical to use f-s2sh for repository

Re: [fossil-users] Scripting fossil

On Feb 18, 2016, at 7:20 PM, Scott Robison wrote: > > As it turns out, this wasn't a great plan. I agree. I even dislike checking configure scripts generated by autoconf and similar into repos. (Please, hold the replies. I already know the justifications. I just

Re: [fossil-users] libfossil scripting mini-demo

On Sat, Feb 20, 2016 at 12:25 AM, Warren Young wrote: > No, libiconv comes to OS X via HPUX -> XPG4 -> SUS -> GNU: > > https://www.gnu.org/software/libiconv/ > https://en.wikipedia.org/wiki/Iconv > > Now that I think more about it, though, I think this isn’t a library >

Re: [fossil-users] repo sharding (was: libfossil scripting mini-demo)

On Feb 18, 2016, at 8:56 AM, Stephan Beal wrote: > > s2> var m = c.loadManifest('current');; > > s2> foreach(m=>k) print(k) I wonder, would it be practical to use f-s2sh for repository sharding? That is, I want to take a single long-lived repo holding several projects

Re: [fossil-users] fossil all remove?

On Feb 19, 2016, at 3:06 AM, Tino Lange wrote: > > How can I get rid of an entry in "fossil all ls -c" for which the > checkout does not exist anymore? Do I need to fiddle with SQL? I think this happens when you nuke a fossil checkout (e.g. via rm -rf) without

Re: [fossil-users] libfossil scripting mini-demo

On Feb 18, 2016, at 7:25 PM, Stephan Beal wrote: > > On Fri, Feb 19, 2016 at 2:34 AM, Warren Young wrote: > fsl_utf8.c:182:10: error: incompatible integer to pointer conversion assigning > to 'char *' from 'int' [-Werror,-Wint-conversion] >

Re: [fossil-users] fossil all remove?

> Should be automatic. When you do "fossil all ls -c", Fossil checks that > each of the check-out directories exists, and removes any that do not > exist from the list. Thanks. The directory still exists (but with some other content now, especially it has no .fslckout file) So I'll move it

Re: [fossil-users] fossil all remove?

On Fri, Feb 19, 2016 at 11:06 AM, Tino Lange wrote: > Hi Fossilers, > > There is no "fossil all remove". > How can I get rid of an entry in "fossil all ls -c" for which the > checkout does not exist anymore? Do I need to fiddle with SQL? > Fossil all recognizes

Re: [fossil-users] fossil all remove?

On 2/19/16, Tino Lange wrote: > Hi Fossilers, > > There is no "fossil all remove". > How can I get rid of an entry in "fossil all ls -c" for which the > checkout does not exist anymore? Do I need to fiddle with SQL? > Should be automatic. When you do "fossil all

[fossil-users] fossil all remove?

Hi Fossilers, There is no "fossil all remove". How can I get rid of an entry in "fossil all ls -c" for which the checkout does not exist anymore? Do I need to fiddle with SQL? Thanks Tino ___ fossil-users mailing list