Segfault in lapd_drift for npes > 2

bendudson / BOUT

NOTE: BOUT++ now at https://github.com/boutproject/BOUT-dev

GNU Lesser General Public License v3.0

24 stars 34 forks source link

Segfault in lapd_drift for npes > 2 #10

Closed bendudson closed 14 years ago

bendudson commented 14 years ago

Running with 4 or more processors, the lapd_drift example case segfaults. Running valgrind on a single processor doesn't give anything obvious. Adding a line like

Field3D tmp = Ni0;

after reading in Ni0 also gives a segfault. Am investigating...

bendudson commented 14 years ago

Seems to be a bug in mesh.load(). Inserting the following in bout++.cpp after the load call gives a segfault on 4 or 8 processors:

Field3D a; a = 0.0; Field3D b = a;

bendudson commented 14 years ago

Caused by mistyping "mesh->xend" instead of "mesh->yend" in Field3D::checkData(). Fixed by 67cfe462c2156a303cb0