On 8/18/2014 19:39, Eric Rubin-Smith wrote:
warning: Can't read pathname for load map: Input/output error.
Core was generated by `/home/eric/fossil-src-20140612172556/fossil update'.
Program terminated with signal 11, Segmentation fault.
#0 0xb75bffb0 in ?? () from
Stephan Beal wrote:
On Tue, Aug 19, 2014 at 7:31 PM, Warren Young war...@etr-usa.com wrote:
On 8/18/2014 19:39, Eric Rubin-Smith wrote:
warning: Can't read pathname for load map: Input/output error.
That looks like a corrupted stack to me.
Try running it under Valgrind.
On Mon, Aug 18, 2014 at 9:39 PM, Eric Rubin-Smith eas@gmail.com wrote:
I have taken a wire capture of the cleartext client-server interaction
and can share that with the devs privately if they would like.
Please
Also, can you reproduce the problem with -O0 instead of -O2 or -Os or
On 8/19/2014 11:50, Eric Rubin-Smith wrote:
Try running it under Valgrind.
I ran it under valgrind already and mentioned the results in the OP --
you probably missed that in my wall of text :-).
No, I just stopped reading when I saw the characteristic smashed stack
gdb output. :)
I configured fossil to use openssl (for https) and built it for Linux
(kernel 3.11.0-12-generic, Ubuntu 13.10). Fossil crashes during the 'pull'
portion of a 'fossil update' or just while running 'fossil pull'. The pull
implies the transfer of a few large artifacts (~60MB range) as well as lots
5 matches
Mail list logo