- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When I break above the select type, I can see the variables in the debugger:
fvec = 0.0d0 select type(br) type is (t_fred) nseg = 10
ie
nseg 1680 INTEGER(4) - fvec {...} REAL(8) fvec(1) 0.000000000000000D+000 REAL(8) fvec(2) 0.000000000000000D+000 REAL(8) fvec(3) 0.000000000000000D+000 REAL(8) fvec(4) 0.000000000000000D+000 REAL(8) fvec(5) 0.000000000000000D+000 REAL(8) fvec(6) 0.000000000000000D+000 REAL(8) fvec(7) 0.000000000000000D+000 REAL(8) fvec(8) 0.000000000000000D+000 REAL(8)
Yet when I step into the select type construct and break at the nseg line, I get in the debugger:
nseg Undefined variable nseg fvec Undefined variable fvec
I suspect it may be a bug in the Windows Integration, I am using 11.1.065.
Is there a workaround I can use to see these variables in the debugger?
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You could pass the relevant variables to a procedure and inspect their values while execution is inside the scope of that procedure.
The integration of the current compiler doesn't have that limitation.
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