Re: [fossil-users] Fuse SIGSEGV

2014-06-27 Thread Andy Goth
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/26/2014 7:11 PM, Andy Goth wrote: On 6/26/2014 3:39 PM, Richard Hipp wrote: Since you are able to repro this, can you rebuild Fossil w/o the -O2 option (so that variables are not optimized out) and rerun in the debugger yet again, then do

Re: [fossil-users] Fuse SIGSEGV

2014-06-27 Thread Andy Goth
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/27/2014 11:51 AM, Andy Goth wrote: On 6/26/2014 7:11 PM, Andy Goth wrote: On 6/26/2014 3:39 PM, Richard Hipp wrote: Since you are able to repro this, can you rebuild Fossil w/o the -O2 option (so that variables are not optimized out) and

[fossil-users] Fuse SIGSEGV

2014-06-26 Thread Andy Goth
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Was trying to run find, eventually got this: Program received signal SIGSEGV, Segmentation fault. 0x76574230 in __strncmp_ssse3 () from /lib64/libc.so.6 (gdb) ba #0 0x76574230 in __strncmp_ssse3 () from /lib64/libc.so.6 #1

Re: [fossil-users] Fuse SIGSEGV

2014-06-26 Thread Richard Hipp
On Thu, Jun 26, 2014 at 4:01 PM, Andy Goth andrew.m.g...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Was trying to run find, eventually got this: Program received signal SIGSEGV, Segmentation fault. 0x76574230 in __strncmp_ssse3 () from /lib64/libc.so.6 (gdb) ba

Re: [fossil-users] Fuse SIGSEGV

2014-06-26 Thread Andy Goth
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/26/2014 3:39 PM, Richard Hipp wrote: Since you are able to repro this, can you rebuild Fossil w/o the -O2 option (so that variables are not optimized out) and rerun in the debugger yet again, then do the same analysis? I have done so, but I