[gnu.gdb.bug] gdb-3.2, printsyms <filename> vs. "---Type <return> to continue---"

shep@ALLSPICE.LCS.MIT.EDU (Tim Shepard) (07/12/89)

I'm using gdb-3.2 on a 4.3BSD Vax.

When printsyms is outputing to a file, it probably shouldn't do this:

(gdb) printsyms /tmp/syms
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
---Type <return> to continue---
(gdb)