{"id":366448,"date":"2024-05-10T14:43:13","date_gmt":"2024-05-10T14:43:13","guid":{"rendered":"\/forum\/forums\/reply\/366448\/"},"modified":"2024-05-10T14:43:13","modified_gmt":"2024-05-10T14:43:13","slug":"366448","status":"publish","type":"reply","link":"https:\/\/innovationspace.ansys.com\/forum\/forums\/reply\/366448\/","title":{"rendered":"Reply To: Ansys 2023 – Material Designer – “MAPDL error”"},"content":{"rendered":"

<p>Hi Yingnan<\/p><p>I’d like to add to what Ashish said regarding the SIG$SEGV error – the cause most likely is a programming issue but it could be something else.  I once saw the cause be a bad network card!  What we also need to focus on is the traceback that is listed – that is the trace of the functions\/libraries.  So MAPDL was using a function in con_int3 when the error happened.  That along with the error being a SIG$SEGV is what we need to look into…and I was not able to find an prior example of this happening with an actual MAPDL release.  Well…it was reported once but when the user ran the model again it did not happen.  And never happened again.  <\/p><p>Are you a commercial customer?  If so please open an technical support call in the standard manner for you.  If you can share the model with technical support and development they may be able to track down the cause.  Development has the skills and tools to track what function MAPDL is calling and the memory stack to figure out what is going on.  Well, the first step would be to see if the issue is repeatable using a different computer to solve.<\/p><p>Mike<\/p><p>p.s. using the Intel BLAS library is not a generic solution.  <\/p><\/p>\n","protected":false},"template":"","class_list":["post-366448","reply","type-reply","status-publish","hentry"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t