- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I decided after a while that using the debugger idbc is not a bad way to debug fortran apps.
My trouble is to set breakponts for subprograms from modules. (I could do it in the past and that is very annoying).
at the moment I grep for the symbol name in the binary and I set the br on it (works perfect).
I would like to go back to my old ways when used to do br mod_name::sub_name
Alin
I decided after a while that using the debugger idbc is not a bad way to debug fortran apps.
My trouble is to set breakponts for subprograms from modules. (I could do it in the past and that is very annoying).
at the moment I grep for the symbol name in the binary and I set the br on it (works perfect).
I would like to go back to my old ways when used to do br mod_name::sub_name
Alin
Link Copied
5 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Alin,
we used to indeed allow the use of the :: operator in earlier versions of IDB. Since this is however not an operator that is supported officially as part of the Fortran syntax we deprecated it. That said you should be be able to simply use the Fortran % operator instead and be able to access subroutines in exactly the same way you were used to.
By the way - have to tried the full blown Intel Debugger GUI by calling idb instead of idbc? This shold add another layer of convenience and ease of use to your debug experience.
Thanks, Rob
we used to indeed allow the use of the :: operator in earlier versions of IDB. Since this is however not an operator that is supported officially as part of the Fortran syntax we deprecated it. That said you should be be able to simply use the Fortran % operator instead and be able to access subroutines in exactly the same way you were used to.
By the way - have to tried the full blown Intel Debugger GUI by calling idb instead of idbc? This shold add another layer of convenience and ease of use to your debug experience.
Thanks, Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Rob,
Thank you very much for you fast answer. Unfortunately it seems % is not really working for me
alin@stokes1:~> idbc ./a
Intel Debugger for applications running on Intel 64, Version 11.1, Build [1.2097.2.270]
------------------
object file name: ./a
Reading symbols from /panfs/panasas/home-alin/a...done.
(idb) br hello%printme
br hello%printme
^
Unable to parse input as legal command or Fortran expression.
Yes I have tried the GUI, indeed very good, but running on top of java on a 64 bit machine it is a nightmare.
Alin
Thank you very much for you fast answer. Unfortunately it seems % is not really working for me
alin@stokes1:~> idbc ./a
Intel Debugger for applications running on Intel 64, Version 11.1, Build [1.2097.2.270]
------------------
object file name: ./a
Reading symbols from /panfs/panasas/home-alin/a...done.
(idb) br hello%printme
br hello%printme
^
Unable to parse input as legal command or Fortran expression.
Yes I have tried the GUI, indeed very good, but running on top of java on a 64 bit machine it is a nightmare.
Alin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A comment - the Windows Fortran debugger uses :: to permit qualification of module symbols. Percent has a specific meaning in Fortran which is not what is wanted here. :: in this context is not meaningful in Fortran, so it works as a notation in the debugger.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Steve Lionel (Intel)
A comment - the Windows Fortran debugger uses :: to permit qualification of module symbols. Percent has a specific meaning in Fortran which is not what is wanted here. :: in this context is not meaningful in Fortran, so it works as a notation in the debugger.
Hate to disagree with Rob and Steve, but neither :: nor % nor %% work. What works is a period.
Reading symbols from /net/spdr62/var/quad/rwgreen/forums/70342/myprog...done.
(idb) br mymod%mysub
br mymod%mysub
^
Unable to parse input as legal command or Fortran expression.
(idb) br mymod%%mysub
br mymod%%mysub
^
Unable to parse input as legal command or Fortran expression.
(idb) br mymod.mysub
Breakpoint 1 at 0x402b42: file /net/spdr62/var/quad/rwgreen/forums/70342/mymod.f90, line 7.
(idb) run
[New Thread 47957749341264 (LWP 23146)]
[New Thread 47957749341264 (LWP 23146)]
Starting program: /net/spdr62/var/quad/rwgreen/forums/70342/myprog
Breakpoint 1, MYMOD::mysub () at /net/spdr62/var/quad/rwgreen/forums/70342/mymod.f90:7
7 print*, "hello"
Is this a bug???
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ron,
. is the right answer for this version...
I have seen in the gui parallel debuging any chance to use it in command line mode?
Alin

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page