public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/61014] [4.7/4.8/4.9/4.10 Regression] gdb can't find symbol of derived data type array in nested subroutine Date: Wed, 30 Apr 2014 13:17:00 -0000 [thread overview] Message-ID: <bug-61014-4-dojQSzznw4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61014-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=61014 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> --- (In reply to Sven Buijssen from comment #0) > (I am not exactly sure whether gfortran or gdb are to blame for this issue, > but I tend towards the former.) > $ gfortran -O0 -g -fno-inline -Wall -Wextra -fno-lto debug.f90 module.o > $ gdb --version > $ ifort -O0 -g -Warn all debug.o module.o > $ idbc a.out As you also have "idb" at hand: You could cross check whether the GCC/gfortran binary works with idbc - and the ifort binary with gdb. They both use the same debugging format (which can differ slightly between versions). > subroutine foo(bar) > type(myint), dimension(:) :: bar This line implies that gfortran uses array descriptors; those are not yet supported in GDB - except that some vendor's versions (e.g. Red Hat/Fedora and (open)SUSE have some basic support. There is an on-going effort to add arrays-descriptor support to GDB; the first step, the support of C99's varying-length arrays has been added a few weeks ago to the GDB trunk. The Fortran support is supposed to come next, but it still will take a couple of weeks. See also: https://github.com/intel-gdb/vla/branches - but the Fortran branch there is a bit outdated. However, ... (In reply to Richard Biener from comment #1) > I get (gdb 7.7): ... > seems that nested function lowering and debugging don't play well together. > Confirmed that it works well with 4.5.x. The combination that it works with 4.5 and that also a SUSE-build of gdb shows the problem, makes it more likely that the problem lies elsewhere. (It might be still a combination of changed dwarf generation in GCC and incomplete GDB support.)
next prev parent reply other threads:[~2014-04-30 13:17 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-30 11:54 [Bug fortran/61014] New: [4.6/4.7/4.8/4.9 " sven.buijssen at math dot uni-dortmund.de 2014-04-30 12:20 ` [Bug debug/61014] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-04-30 12:20 ` rguenth at gcc dot gnu.org 2014-04-30 13:17 ` burnus at gcc dot gnu.org [this message] 2014-04-30 13:24 ` burnus at gcc dot gnu.org 2014-04-30 13:44 ` sven.buijssen at math dot uni-dortmund.de 2014-05-02 19:26 ` burnus at gcc dot gnu.org 2014-05-07 17:38 ` tromey at gcc dot gnu.org 2014-06-12 13:49 ` rguenth at gcc dot gnu.org 2014-12-01 12:00 ` [Bug debug/61014] [4.8/4.9/5 " rguenth at gcc dot gnu.org 2014-12-19 13:44 ` jakub at gcc dot gnu.org 2015-06-23 8:28 ` [Bug debug/61014] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org 2015-06-26 20:19 ` [Bug debug/61014] [4.9/5/6 " jakub at gcc dot gnu.org 2015-06-26 20:39 ` jakub at gcc dot gnu.org 2021-05-14 9:47 ` [Bug debug/61014] [9/10/11/12 " jakub at gcc dot gnu.org 2021-06-01 8:06 ` rguenth at gcc dot gnu.org 2022-05-27 9:35 ` [Bug debug/61014] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:30 ` jakub at gcc dot gnu.org 2023-07-07 10:30 ` [Bug debug/61014] [11/12/13/14 " rguenth at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-61014-4-dojQSzznw4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).