Hi Patrick, That is strange isn't it. One thing to try would be to see if just LOADing the data causes the crash, or if it's something in the graphics crashing as it makes all the overlays, so replace the SHADE with LOAD in your loop. Is the machine where this breaks down a redhat linux system, or something else? Ansley On 1/21/2011 5:50 AM, Brockmann Patrick wrote:
Ansley Manke a écrit :Hi Patrick, When I run Ferret v6.64 on our x86_64_linux machine, the script runs through all 255 files successfully. The gif image is below, and it looks like it is correct. It does not make a difference if I run in batch mode or execute your script from the Ferret command line. As somebody on the list suggested, try canceling memory inside your loop after cancel data. You could also put these commands inside your loop, after cancel data, which might help us find out more about this: show axis/all; show memory/all; show variables In our group we have been talking recently about shared-object libraries that are typically linked with Ferret, and I wonder if inconsistencies with libraries on our different machines could possibly be a problem. That seems to be more of an issue with our 32-bit builds. I see that this executable does not link with a lot of shared object libraries. What is the output of the ldd command on your executable? Here, it shows, > ldd /home/users/tmap/ferret/x86_64-linux/bin/ferret_v664 libdl.so.2 => /lib64/libdl.so.2 (0x0000003aeb000000) libc.so.6 => /lib64/libc.so.6 (0x0000003aea800000) /lib64/ld-linux-x86-64.so.2 (0x0000003aea400000)Hi Ansley, Thanks for testing that crash issue. I have discovered that I have worked on the only machine where the crash occurs... It works everywhere except on a machine x86_64 with ferret (6.3, 6.64) On this machine I get a shared library dependencies as follows $ ldd /usr/local/pub/ferret/6.6/bin/ferret_v664 linux-vdso.so.1 => (0x00007fffb01ff000) libdl.so.2 => /lib64/libdl.so.2 (0x00002afb6666d000) libc.so.6 => /lib64/libc.so.6 (0x00002afb66872000) /lib64/ld-linux-x86-64.so.2 (0x00002afb6644c000) Same as on another x86_64 machine where it runs. Really strange and not easy to understand why it crashes on this specific machine. I have tried all the cleaning and display of information (cancel memory/all ...) Nothing strange is displayed before the crash. Not sure to investigate this further. Thanks to all for you help. Patrick