This subforum is specifically to discuss packaging issues on different platforms (windows, mac, linux), and using different packaging systems (conda, etc...)
sgrogan wrote: ↑Sun May 17, 2020 12:23 pm
Anyway I will try to re-build FreeCAD release with debug symbols using the updated environment and see if we can get a better error message.
Picking up on this https://forum.freecadweb.org/viewtopic. ... 31#p399498
libmesh.dll does not exist in the Conda env.
I have a release build running locally with PDB and without SEH. So hopefully FreeCAD will crash and we will get a good error message.
With the stock build Standard, Mefisto, and gmesh meshes work from Mesh WB, only netgen fails with the access violation on a Part cube.
UR_ wrote: ↑Sun May 17, 2020 1:35 pm
No more insights without debug build of smesh and netgen
Perhaps netgen should be pinned to 6.2.1808 until this is fixed, to get at least working builds.
Thanks! I will try to provide debug builds for netgen and smesh in the next days.
Regarding pinning of 6.2.1808: let's try to solve the issue first. Actually pulling such incompatible versions should never happen. We need to pin things more tightly...
I simple added 500 to the build-number to ensure the debug build is installed if freecad/label/debug is added to the channels. I think this is something we can also apply to other feedstocks to make debug builds easily reproducible: https://github.com/looooo/netgen-feedst ... ddf82dc701
For windows I simple did the following to create the debug build:
debug packages for netgen, smesh (linux and win) are uploaded. Not yet sure if the linux builds are really debug-builds as the size hasn't changed. You can try if updating to debug-packages works by:
looo wrote: ↑Mon May 18, 2020 4:16 pm
debug packages for netgen, smesh (linux and win) are uploaded. Not yet sure if the linux builds are really debug-builds as the size hasn't changed. You can try if updating to debug-packages works by:
Code: Select all
conda update --all -c freecad/label/debug
When running CMake in the env I get some medc errors
I wonder how to create a proper call stack like UR_ posted. When I try meshing with freecad on windows (using debug packages of netgen and smesh) I only get this error message:
Are debug/release builds interchangeable? Is it possible to use a debug netgen and a release smesh, freecad? And if so, do I have to recompile freecad if I build netgen in debug-mode. Somhow I get different errors, trying different combinations.
looo wrote: ↑Tue May 19, 2020 8:41 am
I wonder how to create a proper call stack like UR_ posted. When I try meshing with freecad on windows (using debug packages of netgen and smesh) I only get this error message:
The error message is: c:\users\lo\miniconda3\conda-bld\netgen_1589790409431\work\libsrc\core\array.hpp:519 : index 1 out of range [0,0)
Netgen does range checks only in debug build, so you get this exception here instead of the crash in release mode. It seems like some array is not properly created and then used. A stack trace here would be nice if possible.
I'll try to set this up on windows myself as well.
clackner wrote: ↑Tue May 19, 2020 5:35 pm
Netgen does range checks only in debug build, so you get this exception here instead of the crash in release mode. It seems like some array is not properly created and then used. A stack trace here would be nice if possible.
I'll try to set this up on windows myself as well.
One additional thing I changed on windows between version 6.2.1808 and 6.2.2004 is this options:
`-D USE_NATIVE_ARCH:BOOL=OFF ^`. Somehow azure was failing when this was enabled for 6.2.2004. But I am not sure if this has influence as it is disabled for linux too.
Btw.: great to have you on board of the freecad-community!
Commenting this line makes it possible for me to compile freecad in debug-mode. Let's see if I can provide some more information about the netgen problem.