Re: [Reduce-algebra-developers] reduce on 64-bit gentoo

[Arthur N. <ac...@ca...>]

A memory violation should never happen, and once one has the rest of the 
build can be messed up arbitrarily badly. This is where it becomes truly 
bad that you are experiencing this on an operating system variant that I 
can not reproduce, since that makes it truly hard for me to discover what 
is going on. If you reckon you are a good C-code level debugger of 
significant size programs then at this stage you go
   ./configure --with-csl --enable-debug
and run the Reduce build under gdb passing an option "-x" to CSL/Reduce - 
which option tells it not to try to catch exceptions but to leave them to 
be passed to gdb. That lets you discover just where in the many many 
thousands of lines of code the calamity arises... but it can then be 
because of the delayed effect of corruption introduced earlier.

If we are going to try to dive down to that level I suggest stopping 
sharing the detailed exchanges with the whole group.

Can you make a gentoo virtual machine that matches your world sufficiently 
that it displays the bad behaviour, and find a web-host or file-share site 
that supports big enough files that you can get it to me so I can run it 
in virtualbox and get EXACTLY the experience you are?

          Arthur

On Thu, 8 Oct 2015, Andrey G. Grozin wrote:

> Dear Arthur,
>
> csl-sanity-check.sh does not show anything wrong. But 
> cslbuild/i686-unknown-gentoo2.2/csl/buildlogs/reduce.log shows:
>
> <skipped>
> +++ fl2bf compiled, 43 + 40 bytes
> fl2bfnil6nilnil
> Memory access violation detected
>
> ... continuing after error
>
> +++ Error unset variable: flag
>
> ... continuing after error
>