debugging f2c+gcc (again) 
Author Message
 debugging f2c+gcc (again)

many thanks to the people who have expalined who to use gdb with
f2c+gcc ie.

"break MAIN__ " and the various points about cases sensitivity,
the appending of underscores, and the indexing of arrays.
The problem is that it breaks down when one steps into a subroutine.
Instead of giving the value of the variable "class" gdb gives

(gdb)  p class_
$1 = (long int *) 0xbffe6e44

My question is, how can i get to see the value of my variables?

rob dunne

--
rob dunne

phone (09) 3602819          
   __   _      
  / /  (_)__  __ ____  __
 / /__/ / _ \/ // /\ \/ /  . . .  t h e   c h o i c e   o f   a
/____/_/_//_/\_,_/ /_/\_\              G N U   g e n e r a t i o n . . .



Thu, 21 Aug 1997 15:34:38 GMT  
 
 [ 1 post ] 

 Relevant Pages 

1. Debugging f2c/gcc-compiled Fortran programs with gdb?

2. Help: f2c+gcc for DOS

3. cmd_line args how ? (f2c,gcc)

4. problem compiling f77 with f2c or gcc on redhat 7.0

5. poor performance of f2c + gcc on BSD/OS 2.0

6. f2c+gcc in DOS (djgpp)

7. SuSE 6.2, f2c and gcc

8. Performance of f2c + gcc under Linux vs SunOS F77

9. Performance of f2c + gcc under Linux vs SunOS F77

10. Problems with f2c + gcc on a PC

11. gcc and f2c problem - itime(), idate(), etime(), nint()

12. floating point on Linux with f2c/gcc

 

 
Powered by phpBB® Forum Software