How to debug multiple fortran90 files with GDB

How to debug multiple fortran90 files with GDB

[Hidetoshi CHIBA]

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.

Thanks in advance,

-------

  Hidetoshi Chiba

Re: How to debug multiple fortran90 files with GDB

[Daniel Jacobowitz]

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

Re: How to debug multiple fortran90 files with GDB

[Hidetoshi CHIBA]

[-- 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 --]

Re: How to debug multiple fortran90 files with GDB

[Hidetoshi CHIBA]

[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]

Dear helpers,

The testcase which was attached in my previous email had a mistake.
So, I'd be happy if you check the new testcase attached in this email.

Thanks in advance,

Hidetoshi Chiba



----- 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: 323 bytes --]

Re: How to debug multiple fortran90 files with GDB

[David Lecomber]

On Tue, 2005-09-06 at 14:26 +0900, Hidetoshi CHIBA wrote:
> Dear helpers,
> 
> The testcase which was attached in my previous email had a mistake.
> So, I'd be happy if you check the new testcase attached in this email.
> 
> Thanks in advance,

Hi all,

I've certainly come across this one too.   Often I'd find that one
couldn't add a breakpoint at a function in an included file, until you'd
stepped into that file once.  It can probably be resolved by taking the
'-readnow' option (see google for syntax, am rusty here today) - but
this may not be an option for behemoth sized codes due to the time it
takes.


Regards
David