From a4226e9f55f3ecbc0e52ce7e96d86dd9ab2959b3 Mon Sep 17 00:00:00 2001 From: jthorn Date: Mon, 13 Jun 2005 15:54:32 +0000 Subject: += description of problem where high resolutions cause a core dump, and outline of workarounds git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinInitialData/IDAxiBrillBH/trunk@76 0a4070d5-58f5-498f-b6c0-2693e757fa0f --- doc/documentation.tex | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/doc/documentation.tex b/doc/documentation.tex index cfd981b..96444be 100644 --- a/doc/documentation.tex +++ b/doc/documentation.tex @@ -216,6 +216,21 @@ together with either 4th~order Lagrange or 3rd~order Hermite interpolation (provided by thorn \textbf{AEIThorns/AEILocalInterp}) to get sufficient accuracy. +One problem with such high resolutions is that \textbf{IDAxiBrillBH} +uses an internal multigrid solver which allocates local arrays on the +stack, whose size depends on the $\eta$ and $\theta$ resolutions. +For high resolutions these arrays may exceed system- and/or shell-imposed +limits on the maximum stack size, causing the code to crash (core-dump). +In an ideal world, someone would fix the offending code to allocate +large arrays on the heap. Unless/Until that happens, you can either +use lower resolution :(, or try raising the operating-system and/or +shell stack-size limits. +For example, using \verb|tcsh| the shell command \verb|limit| +shows the current limits, and \verb|limit stacksize unlimited| +raises your limit to as much as the operating system will allow. +Using \verb|bash| the corresponding commands are \verb|ulimit -a| +and \verb|ulimit -s unlimited|. + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \section{Debugging Parameters} -- cgit v1.2.3