Re: [fossil-users] Side-by-side diff broken in version 1.22 on Windows?

Same problem here. Fossil 1.22 runs as a service on a Windows 7 system. When asking for a diff of a single file, fossil sometimes does not respond. However, when asking for a diff for the whole set of files in a checkout, it does not. This does not happen every time. For example, on a clone of th

Re: [fossil-users] Side-by-side diff broken in version 1.22 on Windows?

I compiled with Visual Studio 2005 and the crash occurs at line 404 in diff.c int x = strlen(p->zStart); It fails (access violation) because p->zStart is 0x0050 This happened when I compiled with /Zi (include debug info) Debugging is still difficult because of /O2 (optimize for speed) so I

Re: [fossil-users] Side-by-side diff broken in version 1.22 on Windows?

Compiling with mingw, fossil receives SIGSEGV in in sbsWriteText : int x = strlen(p->zStart); Printing zStart in gdb shows : $2 = 0x7 . In the caller, we have: s.zStart = ""; ... /* nothing here modifies zStart */ sbsWriteText(&s, ...); gdb details follow: > (gdb) bt > #0 0x0

Re: [fossil-users] Side-by-side diff broken in version 1.22 on Windows?

This issue appears to be the same with different compilers then: Compiling with MinGW, with “CFLAGS=-O0 make -f win/Makefile.mingw” the problem disappears. On Mon, Mar 19, 2012 at 11:08, Jos Groot Lipman wrote: > I compiled with Visual Studio 2005 and the crash occurs at line 404 in > diff.c >  

[fossil-users] Open a remote repository?

Is it possible to open a fossil repository that isn't cloned locally? For example, suppose I have a fossil repository stored on a remote server -- can I forgo cloning it and do a straight open, such as: $ fossil open http://dev.mysite.com/myrepo.fossil The benefit of this is that it enforces

Re: [fossil-users] Open a remote repository?

On Mon, Mar 19, 2012 at 11:28, Christopher Berardi wrote: > Is it possible to open a fossil repository that isn't cloned locally? > For example, suppose I have a fossil repository stored on a remote > server -- can I forgo cloning it and do a straight open, such as: > >    $ fossil open http://dev

Re: [fossil-users] Thanks and some questions

>> I notice the .fossil file is created in my home directory when using >> fossil. Because I am testing how fossil works to learn how to use it for my >> workflows, I have created several fossil repos for different test projects >> and then sometimes delete the whole subdirectory containing the rep

Re: [fossil-users] Side-by-side diff broken in version 1.22 on Windows?

I ran the offending diff through valgrind and it turned up one use of an uninitialized variable, though that use seemed harmless to me. The fix is at http://www.fossil-scm.org/fossil/info/9262546e43 - can you try this change and see if that clears the problem? I'm not able

Re: [fossil-users] Side-by-side diff broken in version 1.22 on Windows?

On Mon, Mar 19, 2012 at 13:00, Richard Hipp wrote: > I ran the offending diff through valgrind and it turned up one use of an > uninitialized variable, though that use seemed harmless to me.  The fix is > at http://www.fossil-scm.org/fossil/info/9262546e43 - can you try this > change and see if th

Re: [fossil-users] Side-by-side diff broken in version 1.22 on Windows?

On Mon, Mar 19, 2012 at 8:17 AM, Benoit Mortgat wrote: > On Mon, Mar 19, 2012 at 13:00, Richard Hipp wrote: > > I ran the offending diff through valgrind and it turned up one use of an > > uninitialized variable, though that use seemed harmless to me. The fix > is > > at http://www.fossil-scm.o

Re: [fossil-users] Side-by-side diff broken in version 1.22 on Windows?

It is stable for me too now. I did notice however that the fossil.exe filesize increased from 1115kB to 1324kB, quite a lot for a single memset operation? Jos Groot Lipman _ From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf O

Re: [fossil-users] Side-by-side diff broken in version 1.22 on Windows?

On Mon, Mar 19, 2012 at 9:45 AM, Jos Groot Lipman wrote: > ** > It is stable for me too now. > > I did notice however that the fossil.exe filesize increased from 1115kB to > 1324kB, quite a lot for a single memset operation? > I probably compiled it differently (mingw vs vs2010) or failed to str

Re: [fossil-users] Side-by-side diff broken in version 1.22 on Windows?

On Mon, Mar 19, 2012 at 9:47 AM, Richard Hipp wrote: > > > On Mon, Mar 19, 2012 at 9:45 AM, Jos Groot Lipman wrote: > >> ** >> It is stable for me too now. >> >> I did notice however that the fossil.exe filesize increased from 1115kB >> to 1324kB, quite a lot for a single memset operation? >> > >

Re: [fossil-users] Thanks and some questions

On Mon, Mar 19, 2012 at 4:12 AM, wrote: [snip] > >> I often add programs to the project and I don't always remember to tell > >> fossil about them. What is the correct way to use fossil so when you > work > >> on new projects where you don't have everything that will ultimately be > part > >> o

Re: [fossil-users] bash: ./fossil: cannot execute binary file

Personally, I'm a HUGE fan of static linking for reasons like this! Really -- the fossil executable isn't very large, compared to git; statically linked fossil is 1/4 the size of dynamically linked git. Dynamically linked git even depends on more libraries than dynamically linked fossil. Here's

Re: [fossil-users] bash: ./fossil: cannot execute binary file

On Sun, Mar 18, 2012 at 2:17 PM, Bob Chapman wrote: > > The statically linked fossil worked just fine on Ubuntu 10.04. However, > to my great surprise, the statically linked fossil produced the following > result on Centos 4.9 (<--which I KNOW has just passed its end of life ;) > > $ unz -v fossil

Re: [fossil-users] Thanks and some questions

I wrote about some of the other issues you addressed in another post. >> What should I be doing to make sure fossil knows about all the new code? >> add doesn't seem to work, and stat or chan doesn't flag newly created >> files that I haven't already added. > fossil add file > fossil commit -m '

Re: [fossil-users] Thanks and some questions

On Mon, Mar 19, 2012 at 4:00 PM, wrote: > > > > fossil extra > > > To see the list of "unmanaged" files: > Thank you. It is more "manual" than I was looking for but if that's the way > it works that's the way it works. > Beware of any program that thinks it knows more than you do. -- D. Richa

[fossil-users] strange 'login failed' error on initial repository clone.

Hey everyone. Need a little help... *Problem:* Attempting to clone a recently-created repository gives this error: D:\f\repo>fossil clone http://user:p...@ec2-xxx.compute.amazonaws.com:6969/hekated:\f\repo\hekate.fossil Bytes Cards Artifacts Deltas Sent: 53