Yeah, I misunderstood. That's what I get for reading emails before coffee.
Note, there are some known ASAN issues, specifically with one of our
diagonal assembly tests, but I haven't had the time to make a good fix and
it's not used in our Ratel or fluids work at this time.
On Tuesday, June 13, 2
On Tue, Jun 13, 2023 at 9:18 AM Jeremy Luke Thompson <
jeremy.thomp...@colorado.edu> wrote:
> It's probably easier to trace that sort of thing when building libCEED on
> its own, but it looks like ASAN is complaining about `char
> *source_path_with_name = "";`
>
> Seems like an easy change I can d
It's probably easier to trace that sort of thing when building libCEED on
its own, but it looks like ASAN is complaining about `char
*source_path_with_name = "";`
Seems like an easy change I can do this morning.
On Tuesday, June 13, 2023, Matthew Knepley wrote:
> For some reason, libCEED seems b
On Tue, Jun 13, 2023 at 9:09 AM Jacob Faibussowitsch
wrote:
> What is your full linker command? Make sure it also contains
> -fsanitize=address
>
Thanks! I did not know you needed that. It would be nice if the linker
would error on that.
Matt
> Best regards,
>
> Jacob Faibussowitsch
> (Jaco
What is your full linker command? Make sure it also contains -fsanitize=address
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Jun 13, 2023, at 11:05, Matthew Knepley wrote:
>
> For some reason, libCEED seems broken with Address Sanitizer
>
>
For some reason, libCEED seems broken with Address Sanitizer
*
UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for
details):
