Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 14 Oct 1996 23:10:02 -0700 (PDT)
From:      Lars Koeller <lkoeller@odie.physik2.uni-rostock.de>
To:        freebsd-bugs
Subject:   Re: bin/1785: vgrind didn't work correct! 
Message-ID:  <199610150610.XAA02777@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/1785; it has been noted by GNATS.

From: Lars Koeller <lkoeller@odie.physik2.uni-rostock.de>
To: J Wunsch <j@uriah.heep.sax.de>
Cc: FreeBSD-gnats-submit@freebsd.org, Lars_Koeller@odie.physik2.uni-rostock.de
Subject: Re: bin/1785: vgrind didn't work correct! 
Date: Tue, 15 Oct 1996 08:02:23 +0200

 In message <199610141644.SAA06414@uriah.heep.sax.de>,
 J Wunsch writes:
 
 >As Lars Koeller wrote:
 >
 >>     Vgrind didn't work as described in the manpage:
 >> 
 >>       1) There are no "and the name of  the current function is listed down
 >>          the margin of each page as it is encountered" (cite out of manpage)
 >
 >I have seen them, though it's not clear to me either when vgrind
 >decides to print them and when not.  Maybe they are printed for
 >functions spanning multiple pages only.
 >
 >>       2) No index file is produced. If I understand the manpage right, the 
 >> 	 creation of index (touch ./index)  in the current directory
 >> 	 should produce a index file of the functions, which could be
 >>          printed with 'vgrind -x index' but the file index is always empty.
 >> 
 >
 >j@ida 697% touch index
 >j@ida 698% vgrind -lc++ -p groff kabel.cc > kabel.PS
 >j@ida 699% cat index
 >dump_kabel kabel.cc 3
 >get_kabel kabel.cc 2
 >list_all_kabel kabel.cc 3
 >
 >(Note that the -p option is new in 2.2.)
 >
 >So it works for me.  If it doesn't work for you, i think it's
 >basically the same problem as with the function labelling in 1).
 >
 >(Without a suggested fix, it's unlikely that any person other than
 >Bill Joy will ever dig into this code again.  It looks basically
 >``write-only''. ;-)
 >
 
       After your hint, I've experienced a  little bit with vgrind. And sure
    it works correct, but  only and  really only if  the sources  are passed
    through indent.   Then there are  the  function definitions at  the left
    margin and vgrind  produces an index file.
 
       Perhaps it would be  wise to point  to this assumtions vgrind made in
    the manpage at an  early point. Also  an  option that pases the  sources
    through  indent cound be a nice  extension or a  link  in the 'SEE ALSO'
    section to indent.
 
    Regards
 
    Lars
 -- 
 ________________________________________________________________________
 Lars Köller                  Phone:  +49 381/498-1665, Fax: -1667
 University of Rostock        E-Mail: 
 Department of Physics          Lars_Koeller@odie.physik2.Uni-Rostock.DE
 Universitätsplatz 3          Anonymous ftp:
 D-18051 Rostock (Germany)      ftp://odie.physik2.uni-rostock.de/pub
 
 
 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610150610.XAA02777>