As indicated clearly here:
> mpicc: command not found
The makefile cannot find the 'mpicc' command which is part of MPI.
First try to redo:
% sh autogen.sh --prefix=...
% make
if this still gives the error message above, check your installation
of MPI and/or disable the parallel version (--disable-mpi).
Note also that you should try to update your versions of
gerris/gfsview more often than once a year!
cheers
Stephane
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Gfs-users mailing list
Gfs-...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gfs-users
Neither do I, it must be something peculiar to the way your system is
configured.
> * However, when I export in gnuplot format, the gnuplot files are different.
> ...
> The size of the new gnuplot file is approximately half the size of the
> previous version I had.
Yes, this is due to this patch:
2011-05-27 Stephane Popinet <popinet at users.sf.net>
* Isolines are now continuous (in 2D only)
> * However, generating the gnuplot files from the batch viewer (with the same
> gfv file) gives different results: the resolution is much lower. The script
> I am using is the following:
> (for k in `seq 0 1 9`; do
> if [ -e "file$k.gfs" ]; then
> cat file$k.gfs
> echo "Save file$k.gnu { format = Gnuplot }"
> fi
> done ) | gfsview-batch2D t.gfv
> Should it give the same result as with the interactive viewer? This would be
> very useful for me.
Yes it should. I will look at it.
cheers
Stephane
------------------------------------------------------------------------------
Malware Security Report: Protecting Your Business, Customers, and the
Bottom Line. Protect your business and customers by understanding the
threat from malware and how it can impact your online business.
http://www.accelacomm.com/jaw/sfnl/114/51427462/
Could you please do the following:
% ulimit -c unlimited
% whatever is required to produce the "segmentation fault" above
then you should have a 'core' file in the directory (or 'core.14534'
where 14534 is the id of the process). This is what the 'ulimit'
command tells the system to do i.e. produce core files arbitrarily
big. The core file is a dump of the memory used by the process when it
crashed. This allows to do 'post-mortem debbuging'. The core file is
not human-readable but a debugger such as gdb will know what do with
it.
To use gdb do
% gdb gfsview2D core
gdb> where
which will tell you where in the code the 'segmentation fault'
occurred. Just cut and paste the gdb output and send it to me. thanks.
Stephane
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the
BlackBerry® mobile platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry® DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1
hmm, are you sure it is zero?
What does:
% ulimit -c
return?
2011/9/14 Stephane Popinet <s.po...@niwa.co.nz>:
Dear Stephane,
I have just installed a virtual Ubuntu 10.04 to identify the problem above.
The problem is the same on this new installation (standard Ubuntu installation with the latest versions).
The procedure you gave now returns a result: the "core" file is 3.4G. I have tried to monitor the memory during the crash, and it always stays lower than 30%. It stays at 24.7% during some time, jumps above 28% just before the crash and then crashes.
"
$ gdb gfsview2D core
GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Reading symbols from /usr/bin/gfsview2D...(no debugging symbols found)...done.
[New Thread 2381]
warning: Can't read pathname for load map: Input/output error.
Error while mapping shared library sections:
/tmp/gfsxxSgfM: No such file or directory.
Reading symbols from /usr/lib/libgfsgl2D.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgfsgl2D.so.0
Reading symbols from /usr/lib/libgfs2D-1.3.so.2...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgfs2D-1.3.so.2
Reading symbols from /usr/lib/libgts-0.7.so.5...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgts-0.7.so.5
Reading symbols from /usr/lib/libftgl.so.2...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libftgl.so.2
Reading symbols from /usr/lib/libgtkglext-x11-1.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgtkglext-x11-1.0.so.0
Reading symbols from /usr/lib/libgdkglext-x11-1.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgdkglext-x11-1.0.so.0
Reading symbols from /usr/lib/libGLU.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libGLU.so.1
Reading symbols from /usr/lib/mesa/libGL.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/mesa/libGL.so.1
Reading symbols from /usr/lib/libXmu.so.6...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libXmu.so.6
Reading symbols from /usr/lib/libXt.so.6...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libXt.so.6
Reading symbols from /usr/lib/libSM.so.6...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libSM.so.6
Reading symbols from /usr/lib/libICE.so.6...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libICE.so.6
Reading symbols from /usr/lib/libgtk-x11-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgtk-x11-2.0.so.0
Reading symbols from /usr/lib/libpangox-1.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libpangox-1.0.so.0
Reading symbols from /usr/lib/libX11.so.6...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libX11.so.6
Reading symbols from /usr/lib/libgdk-x11-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgdk-x11-2.0.so.0
Reading symbols from /usr/lib/libatk-1.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libatk-1.0.so.0
Reading symbols from /usr/lib/libpangoft2-1.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libpangoft2-1.0.so.0
Reading symbols from /usr/lib/libgdk_pixbuf-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgdk_pixbuf-2.0.so.0
Reading symbols from /lib/libm.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /usr/lib/libpangocairo-1.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libpangocairo-1.0.so.0
Reading symbols from /usr/lib/libcairo.so.2...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libcairo.so.2
...
Reading symbols from /usr/lib/openmpi/lib/openmpi/mca_coll_tuned.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/openmpi/lib/openmpi/mca_coll_tuned.so
Reading symbols from /usr/lib/openmpi/lib/openmpi/mca_osc_pt2pt.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/openmpi/lib/openmpi/mca_osc_pt2pt.so
Reading symbols from /usr/lib/openmpi/lib/openmpi/mca_osc_rdma.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/openmpi/lib/openmpi/mca_osc_rdma.so
Reading symbols from /usr/lib/openmpi/lib/openmpi/mca_pubsub_orte.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/openmpi/lib/openmpi/mca_pubsub_orte.so
Reading symbols from /usr/lib/openmpi/lib/openmpi/mca_dpm_orte.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/openmpi/lib/openmpi/mca_dpm_orte.so
Reading symbols from /usr/lib/dri/swrast_dri.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/dri/swrast_dri.so
Reading symbols from /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so
Reading symbols from /usr/lib/pango/1.6.0/modules/pango-basic-fc.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/pango/1.6.0/modules/pango-basic-fc.so
Symbol file not found for /tmp/gfsxxSgfM
Core was generated by `gfsview2D gouttes-bin-0.003.gfs t.gfv'.
Program terminated with signal 11, Segmentation fault.
#0 0x00007f98c4fbf745 in ?? () from /usr/lib/libgfs2D-1.3.so.2
(gdb) where
#0 0x00007f98c4fbf745 in ?? () from /usr/lib/libgfs2D-1.3.so.2
#1 0x00007f98c4fbfaed in ?? () from /usr/lib/libgfs2D-1.3.so.2
#2 0x00007f98c4fbfaed in ?? () from /usr/lib/libgfs2D-1.3.so.2
#3 0x00007f98c4fbfaed in ?? () from /usr/lib/libgfs2D-1.3.so.2
#4 0x00007f98c4fbfe05 in gfs_cell_corner_interpolator () from /usr/lib/libgfs2D-1.3.so.2
#5 0x00007f98c4fc0133 in gfs_cell_corner_value () from /usr/lib/libgfs2D-1.3.so.2
#6 0x00007f98c5262195 in ?? () from /usr/lib/libgfsgl2D.so.0
#7 0x00007f98c52622ac in ?? () from /usr/lib/libgfsgl2D.so.0
#8 0x00007f98c5262444 in ?? () from /usr/lib/libgfsgl2D.so.0
#9 0x00007f98c5262444 in ?? () from /usr/lib/libgfsgl2D.so.0
#10 0x00007f98c5262444 in ?? () from /usr/lib/libgfsgl2D.so.0
#11 0x00007f98c5262444 in ?? () from /usr/lib/libgfsgl2D.so.0
#12 0x00007f98c5262444 in ?? () from /usr/lib/libgfsgl2D.so.0
#13 0x00007f98c5262444 in ?? () from /usr/lib/libgfsgl2D.so.0
#14 0x00007f98c5262444 in ?? () from /usr/lib/libgfsgl2D.so.0
#15 0x00007f98c5262444 in ?? () from /usr/lib/libgfsgl2D.so.0
#16 0x00007f98c5262444 in ?? () from /usr/lib/libgfsgl2D.so.0
#17 0x00007f98c5262444 in ?? () from /usr/lib/libgfsgl2D.so.0
#18 0x00007f98c5262444 in ?? () from /usr/lib/libgfsgl2D.so.0
...
---Type <return> to continue, or q <return> to quit---
..."
It is the same as far I have seen.
Best regards,
Marie-Jean.
>> Reading symbols from /usr/bin/gfsview2D...(no debugging symbols
>> found)...done.
There is a problem there. How did you install GfsView? as you can see
it does not include "debugging symbols" i.e. symbols indicating the
correspondance between the executable code and the source code. This
explains why you get lines like:
#0 0x00007f98c4fbf745 in ?? () from /usr/lib/libgfs2D-1.3.so.2
where "??" should contain the position in the source code where the
call occured (this is what we are after).
To fix this you need to install gerris and gfsview from source (which
will include the "-g" option of the compiler which will generate
executables with debugging symbols).
cheers
yes and also:
#0 do_path (cell=0x3f242ba8, i=2, n=0x7ffffe0e44b0, d=0x7f06162b8728,
max_level=-1, centered=0, inter=0x7ffffe0e4550) at fluid.c:2895
2895 d1[l] = path[i][j][l] < 0 ? FTT_OPPOSITE_DIRECTION (d[-
path[i][j][l] - 1]) :
which tells you that the "segmentation fault" occurred at line 2895 of
file fluid.c. These lines are also important:
#9 0x00007f06160abce4 in follow_isoline (cell=0x3f243288, start=0,
gl=0xbcc64300, val=<value optimized out>) at gfsgl2D.h:756
how many lines with follow_isoline do you have?
cheers
Stephane
------------------------------------------------------------------------------
Doing More with Less: The Next Generation Virtual Desktop
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops? How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
OK that explains the crash then. follow_isoline() is calling itself
recursively 50356 times and the stack runs out of memory.
To check that this is the case, try:
% ulimit -s
on my system I get 8192
then do
% ulimit -s 4096
and re-crash the code. If the hypothesis above is correct the code
should now crash after only 50356 / 2 calls to follow_isoline().
There are mostly two reasons this could happen:
1- you do really have an isoline which crosses (more than) 50356
cells. In this case, the algorithm needs to be modified to be able to
handle isolines which cross more than ~50000 cells (this can vary
depending on the size of the memory stack on different systems).
2- there is a bug in the algorithm and it loops endlessly around the
same (closed) isoline. This case should be handled properly by the
current algorithm but there could be a bug.
What do you think? Is 1- plausible for your particular simulation file?
Could you please apply the attached patch to a clean checkout of gfsview i.e.
% darcs get http://gerris.dalembert.upmc.fr/darcs/gfsview-stable
% cd gfsview-stable
% darcs apply /tmp/isopatch
% sh autogen.sh --prefix=...
% make && make install
and retry to generate very long isolines. The patch removes the
useless function recursion and should fix the problem. Please also
check that the isolines generated look OK.
Once I get your confirmation, I will push the patch to gfsview-devel.
cheers
Stephane
Great, thanks for your help in tracking the bug.
> However, the other issue still appears. If I do the command "$ gerris2D -e
> "GfsOutputView test.gnu { format = Gnuplot } t.gfv" file.gfs > /dev/null",
> it still gives a different result than with the interactive viewer (27K
> instead of 3.6M). I don't know if this is related to gfsview.
Yes, this is a different bug. I can reproduce it here. I will have a look.
cheers
Stephane
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
> I have followed your instruction and the patch is working.
> When I download the gfsview tarball from
> http://gfs.sourceforge.net/wiki/index.php/Download, I get
> gfsview-snapshot-110913.
> The fix is added on the log at 110919. Is the gfsview tarball updated?
To make sure, you can look at the 'ChangeLog' file in the tarball. As
you can see, the recent patch is not in this tarball. So the tarball
has not been updated (this should be done automatically). I will check
what happened. Thanks for reporting the problem.
Stephane
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2