- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I am using dbx to debug and right after a goto statement the debugger says 'An type was presented during execution of the previous command...' The goto statement does land the program after an entry statement. Can that cause this behavior? The opaque type is only present in the sva7 portion of sva1.f
(idb) where
0 0x8233d68 in sva7_(...) "sva1.f":1
1 0x82264f8 in sv() "sv.f":209
2 0x81906a2 in dim1() "dim1.f":194
3 0x805c562 in qtx0() "qtx0.f":1509
4 0x8051073 in qtx() "qtx.f":937
5 0x804a0ca in main$q_$BLK() "qtmain.f":1
6 0x82aa3d0 in main(...) in qtx
7 0x42015574 in __libc_start_main(xxx) in /lib/tls/libc.so.6
8 0x8049f81 in _start(...) "../sysdeps/i386/elf/start.S":81
I am compiling with ifort 8.0-c -Vaxlib -g *.f
and then ifort -o exeName -g *.o
Because of this, I cannot print out any variables in the sva7 portion of the program. How can i fix this? The program is in working condition.
I am using dbx to debug and right after a goto statement the debugger says 'An
(idb) where
0 0x8233d68 in sva7_(...) "sva1.f":1
1 0x82264f8 in sv() "sv.f":209
2 0x81906a2 in dim1() "dim1.f":194
3 0x805c562 in qtx0() "qtx0.f":1509
4 0x8051073 in qtx() "qtx.f":937
5 0x804a0ca in main$q_$BLK() "qtmain.f":1
6 0x82aa3d0 in main(...) in qtx
7 0x42015574 in __libc_start_main(xxx) in /lib/tls/libc.so.6
8 0x8049f81 in _start(...) "../sysdeps/i386/elf/start.S":81
I am compiling with ifort 8.0-c -Vaxlib -g *.f
and then ifort -o exeName -g *.o
Because of this, I cannot print out any variables in the sva7 portion of the program. How can i fix this? The program is in working condition.
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - rfleming121
Hello,
I am using dbx to debug and right after a goto statement the debugger says 'An type was presented during execution of the previous command...' The goto statement does land the program after an entry statement. Can that cause this behavior? The opaque type is only present in the sva7 portion of sva1.f
(idb) where
0 0x8233d68 in sva7_(...) "sva1.f":1
1 0x82264f8 in sv() "sv.f":209
2 0x81906a2 in dim1() "dim1.f":194
3 0x805c562 in qtx0() "qtx0.f":1509
4 0x8051073 in qtx() "qtx.f":937
5 0x804a0ca in main$q_$BLK() "qtmain.f":1
6 0x82aa3d0 in main(...) in qtx
7 0x42015574 in __libc_start_main(xxx) in /lib/tls/libc.so.6
8 0x8049f81 in _start(...) "../sysdeps/i386/elf/start.S":81
I am compiling with ifort 8.0-c -Vaxlib -g *.f
and then ifort -o exeName -g *.o
Because of this, I cannot print out any variables in the sva7 portion of the program. How can i fix this? The program is in working condition.
I am using dbx to debug and right after a goto statement the debugger says 'An
(idb) where
0 0x8233d68 in sva7_(...) "sva1.f":1
1 0x82264f8 in sv() "sv.f":209
2 0x81906a2 in dim1() "dim1.f":194
3 0x805c562 in qtx0() "qtx0.f":1509
4 0x8051073 in qtx() "qtx.f":937
5 0x804a0ca in main$q_$BLK() "qtmain.f":1
6 0x82aa3d0 in main(...) in qtx
7 0x42015574 in __libc_start_main(xxx) in /lib/tls/libc.so.6
8 0x8049f81 in _start(...) "../sysdeps/i386/elf/start.S":81
I am compiling with ifort 8.0-c -Vaxlib -g *.f
and then ifort -o exeName -g *.o
Because of this, I cannot print out any variables in the sva7 portion of the program. How can i fix this? The program is in working condition.
Let me point out two things: 1) V8.0 is about 7 years old, and was the first CVF->ifort translation. And, the debug generation was a bit"sparse"at first. 2) You haven't shown us your program, so I can't say anything about what the variables might look like :-)
If you cannot upgrade your compiler to a newer release, I'm thinking you'll need to use "print" statements to debug anything in the "sva7" portion of your program.
- Lorri

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