https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758
--- Comment #20 from paul.richard.thomas at gmail dot com <paul.richard.thomas at gmail dot com> --- Hi Dmitry, I will persist with 81758 until I have a satisfactory testcase and then I promise that I will move to 80850. Cheers Paul On 26 October 2017 at 15:20, liakhdi at ornl dot gov <gcc-bugzi...@gcc.gnu.org> wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758 > > --- Comment #19 from DIL <liakhdi at ornl dot gov> --- > Hi Paul, > > Great, thanks a lot! That was pretty quick. Upon a chance, as there is still a > momentum :), could you please take a brief look at bug #80850 to see whether > it > may be related since you mentioned "allocation with source" in the previous > comment? That's exactly what 80850 is about. If fails to allocate a previously > nullified pointer with a sourced allocate(), complaining that the pointer is > already allocated. From what I could deduce from valgrind, somehow the code > produced by the sourced allocate() here encounters a corrupted internal > pointer > representation. If you need any debugging information/screenshots from me, I > will be happy to provide (I did not really see an easy way to reduce the > code). > > -- > You are receiving this mail because: > You are on the CC list for the bug.
