Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site unc.UUCP Path: utzoo!watmath!clyde!floyd!harpo!decvax!mcnc!unc!tim From: tim@unc.UUCP (Tim Maroney) Newsgroups: net.lang.c Subject: Re: C optimization and debugging. Message-ID: <6890@unc.UUCP> Date: Thu, 8-Mar-84 13:59:57 EST Article-I.D.: unc.6890 Posted: Thu Mar 8 13:59:57 1984 Date-Received: Sat, 10-Mar-84 08:47:49 EST References: <903@qubix.UUCP> Organization: CS Dept., U. of N. Carolina at Chapel Hill Lines: 16 Another feature that is desperately needed in C debuggers is an easy way to follow linked data in the memory of a process. By linked data I mean such data structures as parse trees, linked lists, etc. This extracting pointer addresses, writing them down, and typing them in stuff is for the birds; it often takes an excruciatingly long time to look over the nodes of a simple parse tree by this means. Better display of structs is also much-needed. The debuggers I've used force you to pull things out a member at a time, a very slow process when you need to look at several members for a number of structs. -- Tim Maroney, University of North Carolina at Chapel Hill mcnc!unc!tim (USENET), tim.unc@csnet-relay (ARPA) All opinions expressed herein are completely my own, so don't go assuming that anyone else at UNC feels the same way.