🚀 go-pugleaf

I am using gdb version 3.3 on Sun 3/50 running SunOS 4.0.

If I compile a program with `cc' and debug it with `gdb', I can't
step over library function calls using the `next' command, nor can
I use library functions while evaluating expressions within gdb
(with `print' or `set' commands). If the program is compiled with
`gcc,' however, the above problems go away. 

When I issue the `next' command to step over a `printf' call, gdb
steps into `etext().' When I use a library function, say `memcpy'
(which is linked into the object code), it complains that `memcpy' 
symbol is not in current context.

Try this experiment with the following program. Try stepping over
the last two statements, and try the command `set memcpy(b, a, 12)'
from within gdb.

#include <memory.h>
main()
{
  int a[3], b[3]; 

  a[0] = 0;
  a[1] = 1;
  a[2] = 2;

  memcpy(b, a, 3*sizeof(int));
  printf("b = {%d, %d, %d}\n", b[0], b[1], b[2]);

} 

-- Hira.
   ha@cs.purdue.edu