🚀 go-pugleaf

I have noticed a bug in the gdb-4.6 when running on a rs/6000 machine. 

When I load a program and run it, it works fine. But if I recompile the
program, and ask gdb to run it again without explicitly reloading it, gdb
gets into a infinite loop; on other machines, gdb determines itself that the
executable is newer and reloads it itself. 

An example session is follows.
----------------------------------------------------------------------------
Current directory is /lido/haider/research/solalg/svd/twops/

(gdb) run
Starting program: /lido/haider/research/solalg/svd/twops/svd.noprof 4 6
matrix size = 4, sweeps = 6
  
****************************************************************************
The program ran and gave some output.
After this I recompiled the program and typed run as below.
****************************************************************************  
  
(gdb) run 4 6
The program being debugged has been started already.
Start it from the beginning? (y or n) y
`/lido/haider/research/solalg/svd/twops/svd.noprof' has changed; re-reading symbols.
`/lido/haider/research/solalg/svd/twops/svd.noprof' has changed; re-reading symbols.
  
****************************************************************************
This line keeps on repeating till I hit C-c C-c
****************************************************************************
(gdb) Quit

----------------------------------------------------------------------------

I have the same code compiled for a sparc, and there it runs correctly.
Has someone else noticed it, has this been discussed. Would someone send a
correction to this if there is one, etc etc.
Please reply by email if you can, I usually don't follow this newsgroup.
Thanks,
--
Haider