🚀 go-pugleaf

Relay-Version: VMS News - V6.0 1/9/90 VAX/VMS V5.3; site kontu.utu.fi
Path: kontu.utu.fi!polaris.utu.fi!news.funet.fi!sunic!mcsun!unido!isaak!escher!nadia!smurf!
 ira.uka.de!sol.ctr.columbia.edu!zaphod.mps.ohio-state.edu!wuarchive!uunet!tut.cis.ohio-state.edu!dingus.sps.mot.com!murf
Newsgroups: gnu.gdb.bug
Subject: It's pretty irritating......next steps into libc routines
Message-ID: <9010111641.AA01622@dingus.>
From: murf@dingus.sps.mot.com (Steve Murphy)
Date: 11 Oct 90 16:41:59 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Approved: bug-gdb@prep.ai.mit.edu
Lines: 47

GDB3.5
sunos 4.0.3

also gdb 3.4
sunos 4.0.3
sunos3.5

code compiled with sunx' cc.


Wouldn't you get irritated? Look at this session:

(gdb) n
66		double	updateRate = 5.0;
(gdb) n
68		str = "fullrwy";
(gdb) n
70		if ((file = fopen(str, "r")) == (FILE *) NULL) {
(gdb) n
0x20128 in etext ()
(gdb) n
Current function has no line number information.
Single stepping until function exit.
0xedda09c in ?? ()
(gdb) n
Current function has no line number information.
No data available on pc function.
(gdb) n
Current function has no line number information.
No data available on pc function.
(gdb) n
Current function has no line number information.
No data available on pc function.
(gdb) n
Current function has no line number information.
No data available on pc function.
(gdb) n
Current function has no line number information.
No data available on pc function.


Why would anyone like to single step thru library routines?
This really is a bad feature.

gdb is nice to code compiled with gcc tho. But, hey...

murf