Frank,
I am running into some unexpected behavior when parsing the input for a uniaxialMaterial that I am developing. If I try to get more arguments than there are, for example by calling OPS_GetString(…) to check if there is any optional input, it results in a segmentation fault.
In "elementAPI.cpp" there is code to check if the current argument exceeds the number of arguments. However, it looks as if "currentArg" is acting like it is zero indexed and "maxArg" is acting like it is 1 indexed (since it is set to the argument count), making the statement "currentArg > maxArg" incorrect for determining if the number of arguments has been exceeded.
Thanks,
Mark
Seg fault when parsing input for a uniaxialMaterial
Moderators: silvia, selimgunay, Moderators