🚀 go-pugleaf

>From uucp Mon Oct 15 03:50 WST 1990 remote from nixsin
To: nixpbe!unido!gnu-gdb-bug
Path: nixsin!nixpbe!nixbur!linus!agate!apple!sun-barr!rutgers!tut.cis.ohio-state.edu!UCSD.EDU!breynolds
From: breynolds@UCSD.EDU (Bill Reynolds)
Newsgroups: gnu.gdb.bug
Subject: (none)
Message-ID: <9009300548.AA27838@inls1.ucsd.edu.UCSD.EDU>
Date: 30 Sep 90 05:48:45 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 11


On our Sun4/330, gdb, v3.5, works great, but on our Sun4/110, there's a problem:
next and step will both step into standard c functions like
printf().  "next" will step over a funtion I've defined no problem, but if
it is asked to go over printf, it enters printf, saying that it doesn't know 
where it is and will single step from now on. I've kludged this by 
defining "n" to be "until +1", but it would be nice to have the full 
functionality of the next command. I'm not sure if this is a bug or a 
screwup of mine, but I thought I'd share it with you.
							Bill Reynolds
							Physics Dept.
							UCSD