This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/81758] [7/8 Regression] [OOP] Broken vtab


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758

--- Comment #17 from paul.richard.thomas at gmail dot com <paul.richard.thomas at gmail dot com> ---
Hi Dmitry,

That's great. I'll let you know how I get on when I return. I knew
that it had to be a complicated pointer assignment or allocation with
source but couldn't deduce it by deep thought :-(

Cheers

Paul


On 23 October 2017 at 19:28, liakhdi at ornl dot gov
<gcc-bugzilla@gcc.gnu.org> wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81758
>
> --- Comment #16 from DIL <liakhdi at ornl dot gov> ---
> Hi Paul,
>
> Thanks for looking into this issue. I ran the debugger again. The vtab
> corruption occurs upon the first encounter in function VectorIterElement() in
> line 720 of gfc_vector.F90. Just to make sure, that line begins with:
> elem_p=>this%container%vec_tile(q(4))%...
> Before that line, the elem_p (cep) vtab looks fine. After that line it gets
> bad. Please let me know if you need more information from the debugger.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]