From: "Hidetoshi CHIBA" <hidetoshi_c@hotmail.com>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: <gdb@sources.redhat.com>
Subject: Re: How to debug multiple fortran90 files with GDB
Date: Mon, 05 Sep 2005 15:58:00 -0000 [thread overview]
Message-ID: <BAY102-DAV43DF8956DB87EE5AD878A9AA40@phx.gbl> (raw)
In-Reply-To: <20050905140128.GB27407@nevyn.them.org>
[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]
> Sorry, we can't help you without a testcase.
OK.
Could you try the testcase attached in this email?
You can use "compile.bat" for compile.
Then, on GDB, set a breakpoint at anywhere in "main.f90", for example on the
line #7 in "main.f90", then after running, please try to print variable
"itest".
In my case, it is not possible to refer to the variable "itest" defined in
"test.f90" from "main.f90".
----- Original Message -----
From: "Daniel Jacobowitz" <drow@false.org>
To: "Hidetoshi CHIBA" <hidetoshi_c@hotmail.com>
Cc: <gdb@sources.redhat.com>
Sent: Monday, September 05, 2005 11:01 PM
Subject: Re: How to debug multiple fortran90 files with GDB
> On Mon, Sep 05, 2005 at 07:24:06PM +0900, Hidetoshi CHIBA wrote:
>> I have a problem on debugging my application which is generated by
>> multiple
>> fortran90 files with GDB.
>> GDB seems not to read a value which is defined in a different fortran90
>> file.
>> Or, is this a problem due to compiler?
>> I usually use "g95" or "f90" for compile.
>> Please tell me how to solve this problem.
>
> Sorry, we can't help you without a testcase. However, I know that g95
> has had some problems emitting correct debugging information in the
> past.
>
> --
> Daniel Jacobowitz
> CodeSourcery, LLC
>
[-- Attachment #2: test.lzh --]
[-- Type: application/octet-stream, Size: 341 bytes --]
next prev parent reply other threads:[~2005-09-05 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 10:23 Hidetoshi CHIBA
2005-09-05 14:01 ` Daniel Jacobowitz
2005-09-05 15:58 ` Hidetoshi CHIBA [this message]
2005-09-06 5:26 ` Hidetoshi CHIBA
2005-09-06 7:04 ` David Lecomber
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=BAY102-DAV43DF8956DB87EE5AD878A9AA40@phx.gbl \
--to=hidetoshi_c@hotmail.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
/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: link
Be 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).