Hi Daniel,
Daniel Grauer <grauer.d(a)gmail.com> writes:
> thanks for the quick answer and the heads up on the update.
I've just looked into the crash that I had found, and it turns out the
test was feeding triangle bad input data, which was causing the
issue. As a result, I suspect that the crash you are seeing is likely
unrelated. As a start, it'd be great if you could obtain a GDB backtrace
of the crash. (assuming you're on Linux) Check various tutorials online
for how to do that.
Best,
Andreas
Hi Daniel,
Daniel Grauer <grauer.d(a)gmail.com> writes:
> about a year ago i created a small gui to use your meshpy in blender,
> unfortunately there is something that causes a crash when i run meshpy in
> certain situations.
> i tried to find the source of the crash but since im not to good with
> coding and it seems the crash happens within _tetgen.pyd i would be glad
> to get some assistance from your side.
>
> so i would be glad if you could contact me.
I've been observing some crashes in my continuous integration tests for
MeshPy. My first attempt would be to upgrade to the newest version of
TetGen, which I've held off on because it loses the ability to do
periodic boundary conditions. (not important for you I'm guessing, but
at one point I cared)
I'll do that sometime soon and let you know. (Also make sure you keep
the mailing list in the loop. Thanks!)
Andreas
