Silvio a Beccara wrote:
Hi Frank,
thanks for the hints: another question, is there a way of using run-gpc in a
(gpc-run, as I corrected myself in another thread.)
parallel environment, i.e. with mpi? In this case one runs programs by means of the script mpirun, but I see no way of using both at the same time... so maybe there's a compiler directive to give more verbose error messages, in order for one to be able to spot the errors without manually dissecting the code?
I have no experience with mpi, and I don't know mpirun, so I can't help here directly. However, the main thing that gpc-run is to run the program with the option --gpc-rts=-E... (you might also consider --gpc-rts=-F...; run a GPC compiled program with --gpc-rts=-h for details). This gives more information, in particular a backtrace. Afterwards, it uses addr2line to translate the error and backtrace locations into routine names and source code positions. You can probably do the same things differently to integrate them with mpi. First, I suggest to play around with those options and addr2line manually, to get a feeling for the things and how to combine them with mpirun. Frank -- Frank Heckenbach, frank@g-n-u.de, http://fjf.gnu.de/, 7977168E GPC To-Do list, latest features, fixed bugs: http://www.gnu-pascal.de/todo.html GPC download signing key: ACB3 79B2 7EB2 B7A7 EFDE D101 CD02 4C9D 0FE0 E5E8