For the last 2-3 days I am chasing a very nasty bug. I am not sure what causes it. It involves a mixture of gsl, floating point operations and memory allocation. Basically, if I allocate memory and write to it and then free it just before a call to gsl ode solver I get segmentation fault. It I do not do it then I get error 0037 (floating point error) though later in one of the next loops. In any case I am not sure if I found the bug but here is what I found. Start bigforth and do:
also dos 100 allocate throw dup 1 swap ! free throw I have tried the trick at three different systems and two different versions of bigforth. All of them consistently give the following: *** glibc detected *** bigforth: munmap_chunk(): invalid pointer: 0x1008cca0 *** ======= Backtrace: ========= /lib/tls/i686/cmov/libc.so.6(cfree+0x1bb)[0xb7e6df5b] [0x1007c832] ======= Memory map: ======== and so on However, all those were 32bit systems. When I have tried it at a 64bit machine everything worked smoothly. Unfortunately the machine is not usable to me since bigforth does not bind libraries (64bit) there: liblapack.so.3 Library not found! Though the first problem is critical for me. May be the fact that it is not seen at 64bit machines can help finding the bug. Thanks! -- Sergey --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
