This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/80850] Sourced allocate() fails to allocate a pointer
- From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 30 May 2017 20:14:54 +0000
- Subject: [Bug libfortran/80850] Sourced allocate() fails to allocate a pointer
- Auto-submitted: auto-generated
- References: <bug-80850-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80850
--- Comment #6 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to DIL from comment #4)
> Offset of zero is fine. I have never observed this SegFault before. I ran
> the test on multiple machines with GCC/5.3.0, GCC/5.4.0, and GCC/6.3.1.
> Also, as I mentioned before, the test passed the VALGRIND check. Would you
> be able to point me to the specific line of the deepest user-level procedure
> in the call stack where the segfault occurs? Was it line 744 of
> __gfc_vector_MOD_vectoriterelementvalue (from your previous comment)?
I set the breakpoint which you see in comment 3. I then ran the program. After
the brak I simply stepped with the n (next) command until the segfault
occurred. So yes at line 744 as shown.