Mon 24 Jul 2017 08:43:52 PM UTC, comment #7:
For the moment, I'm going to close this report. There is enough other stuff going on that needs attention. I've got another project that I could use your help on. I'll file a different bug report about that.
|
Mon 24 Jul 2017 07:01:53 PM UTC, comment #6:
To get a "second opinion" I recompiled with clang-4.0.0
0fb64e83f8b3 tip @
The only problem I see is
So perhaps we should declare those errors false positives, at least for now.
Dmitri.
--
|
Mon 24 Jul 2017 05:32:14 AM UTC, comment #5:
Looks the same.
Dmitri.
--
|
Mon 24 Jul 2017 05:05:06 AM UTC, comment #4:
This may be undoing an optimization, but try the attached 51552.diff and see if it helps.
(file #41311)
|
Mon 24 Jul 2017 04:33:47 AM UTC, comment #3:
Here is some other tests resultin in the same error:
|
Mon 24 Jul 2017 04:21:27 AM UTC, comment #2:
|
Mon 24 Jul 2017 04:16:43 AM UTC, comment #1:
Can you try starting Octave and just execute this one command?
I'm trying to figure out whether it is something to do with exception processing.
If that segfaults (I hope it will) then does the following work?
|
Mon 24 Jul 2017 01:53:56 AM UTC, original submission:
When built with "enable-address-sanitizer-flags" octave crashed
in multiple tests with
error. (Array.h is attached)
E.g. running
(full log is attached).
One needs to have at least gcc 7 to get stack-use-after-scope diagnostic. See
Dmitri.
--
|