Sponsored Content
Full Discussion: wdb debugger
Top Forums Programming wdb debugger Post 11560 by Sven28 on Friday 7th of December 2001 11:44:07 AM
Old 12-07-2001
thx helped very much
 

2 More Discussions You Might Find Interesting

1. Programming

How to debug with wdb debugger a cobol program?

Hi Forum, i have such a question. I have a cobol program which is calling a C program and in that C program i get a core dump:(. I want to investigate what is the issue using WDB debuger, but a dont see the code from COBOL program in the debuger, when i run the debugger with the exe!!! ... (2 Replies)
Discussion started by: vovan
2 Replies

2. Programming

Alternative debugger to GNU insight debugger

GNU insight debugger is not available now a days and it is required to debug/inspect assembly code as written in the book Assembly Language Programming step by step in Linux so my question is; is there any alternative to insight that I can use instead of insight in which I can get the same... (5 Replies)
Discussion started by: vectrum
5 Replies
CALLGRIND 
ANNOTATE(1) Release 3.9.0 CALLGRIND ANNOTATE(1) NAME
callgrind_annotate - post-processing tool for the Callgrind SYNOPSIS
callgrind_annotate [options] [callgrind-out-file [source-files...]] DESCRIPTION
callgrind_annotate takes an output file produced by the Valgrind tool Callgrind and prints the information in an easy-to-read form. OPTIONS
-h --help Show summary of options. --version Show version of callgrind_annotate. --show=A,B,C [default: all] Only show figures for events A,B,C. --sort=A,B,C Sort columns by events A,B,C [event column order]. --threshold=<0--100> [default: 99%] Percentage of counts (of primary sort event) we are interested in. --auto=<yes|no> [default: no] Annotate all source files containing functions that helped reach the event count threshold. --context=N [default: 8] Print N lines of context before and after annotated lines. --inclusive=<yes|no> [default: no] Add subroutine costs to functions calls. --tree=<none|caller|calling|both> [default: none] Print for each function their callers, the called functions or both. -I, --include=<dir> Add dir to the list of directories to search for source files. SEE ALSO
valgrind(1), $INSTALL/share/doc/valgrind/html/index.html or http://www.valgrind.org/docs/manual/index.html. AUTHOR
Josef Weidendorfer <Josef.Weidendorfer@gmx.de>. This manual page was written by Philipp Frauenfelder <pfrauenf@debian.org>. Release 3.9.0 11/01/2013 CALLGRIND ANNOTATE(1)
All times are GMT -4. The time now is 06:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy