mlohry

Stack trace back to the originating source here if it helps: ``` ================================================================= ==1366268==ERROR: AddressSanitizer: heap-use-after-free on address 0x60b00034a290 at pc 0x7f388fe38f2d bp 0x7ffdc807bc50 sp 0x7ffdc807b3f8 WRITE of size 104...

@davidbeckingsale 's [comment on an umpire issue here](https://github.com/LLNL/Umpire/issues/699#issuecomment-1048280946) made me think to try building my application with static libraries. This actually "works" and the program finalizes without issue, but the...

Hi @cyrush , I actually just ran into this on latest develop branch on MacOS with gcc-12. Any idea for a workaround? ``` [2/123] Linking CXX shared library lib/libascent_flow.dylib FAILED:...

platform: ``` ~/dev/ascent/build$ sysctl -n machdep.cpu.brand_string Apple M2 Max ~/dev/ascent/build$ sw_vers ProductName: macOS ProductVersion: 13.6.2 BuildVersion: 22G320 ```

This is with homebrew gcc-12, and the "classic" xcode linker. #730 I've temporarily worked around by commenting out the `template class FLOW_API DataWrapper` declaration.

Hi @cyrush , looking back I'm unclear on this statement > On most platforms we compile with ints are 64-bits but it looks like the build state now is that...

Sounds good @cyrush , I'll work around it for the time being. Happy to test a branch fix when the time comes.

Thank you @cyrush !!

@cyrush thanks, that should work, will give it a try.

In the above bad image, I was giving conduit/ascent only the connectivity for the surface elements, but it still had all the solution and coordinate information for the volume vertexes....