Skip to main content

function call flow tool for C


1. tceetree (http://sourceforge.net/p/tceetree/wiki/Home/)

tceetree could be useful for you when:
  • you have the sources of an application written in C language;
  • you would like to have a graphical representation of the entire or partial function call tree.
If this is what you are looking for, follow these steps:
  1. Install (and compile) CScope. A compiled Windows executable can be found here. For a compiled Linux executable search the Web e.g. for a cscope RPM or Debian package.
  2. Install Graphviz.
  3. Go to your sources root directory and do:
    • under Windows: dir /B /S *.c > cscope.files (/B = bare format, no extra info);
    • under Linux: find . -name '*.c' > cscope.files;
      that will recurse subdirectories and list all C files in cscope.files.
  4. execute cscope -b -c -R (build the cross reference only, don't compress it, recurse);
  5. run tceetree with cscope.out as input (default) to get tceetree.out (DOT language representation of function call tree);
  6. execute dot -Tpng -O tceetree.out to get a graphical representation of the tree in tceetree.out.png.
There are a lot of options you can specify when invoking dot to customize the graph, for example:
  • you can change output format e.g. to pdf: dot -Tpdf -O tceetree.out;
  • you may modify layout from left to right instead of top to bottom: dot -Grankdir=LR -Tpng -O tceetree.out;
  • you may modify graph, nodes and edges font: dot -Gfontname=Helvetica -Nfontname=Helvetica -Efontname=Helvetica -Tpng -O tceetree.out;
  • see dot.1.pdf and dotguide.pdf within Graphviz documentation for many other options.
You may wish to give a try to one of the other tools provided by Graphviz instead of dot (see dot.1.pdf for a list).
This is the synopsis of tceetree:
tceetree [-c <depth>] [-C <depth>] [-d <file>] [-f] [-F] [-h] [-i <file>] [-o <file>] [-p <function>] [-r <root>] [-s <style>] [-v] [-V] [-x <function>]
OptionDescription
-c <depth>Depth of tree for called functions: default is max. Depth is measured starting from root(s) function(s).
-C <depth>Depth of tree for calling functions: default is 0. Depth is measured starting from root(s) function(s) in backward direction.
-d <file>Output a shortened cscope output file: default is no output. The shortened file includes only function information and can be used as input (-i) for following calls to tceetree to increase speed on big projects.
-fPrint the file name where the call is near to branch.
-FGroup functions into one cluster for each source file.
-hPrint help.
-i <file>Input cscope output file: default is cscope.out.
-o <file>Output file for graphviz: default is tceetree.out.
-p <function>Highlight call path till function. Path starts from root(s) till the specified function (only one), in backward or forward direction.
-r <root>Root function of tree: default is main. This option may occur more than once for multiple roots (max 5).
-s <style>Style for highlight call path: 0 = red color (default); 1 = blue color; 2 = green color; 3 = bold; 4 = dashed; 5 = dotted.
-vPrint version.
-VVerbose output (mainly for debugging purposes).
-x <function>Function to be excluded from tree. This option may occur more than once for multiple functions (max 20). -x LIBRARY is a special case for excluding all library functions, i.e. not found defined in any file. All the functions, called (calling) directly or indirectly from the excluded one(s) only, will be excluded too.
tceetree can be called with no option at all: default options will be used.
Examples:
  • Screenshot #1 was done with tceetree -F -x LIBRARY;
  • screenshot #2 was done with tceetree -C max -r gettree -p ttreefindnode.

2. cflow (http://www.gnu.org/software/cflow/)

# cflow main.c
# cflow -d 10 main.c
# cflow -m StartFunction main.c

-d : depth
-m : start function name

Comments

Popular posts from this blog

sanitize on in CMakeLists.txt

1. CMakeLists.txt set(CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} -fsanitize=address") add_compile_options(-fsanitize=address) If a subdir is set with add_subdirectory and a module that does not support sanitize is imported from the path and needs to be removed, add -fno-sanitize=address to add_compile_options in CMakeLists.txt of the subdir to remove it. Basically, if you enable sanitize, sanitize will adjust ulimit's core to 0, so core will not occur. You can do this by putting the following part as an environment variable. (Below is the part you put in systemd's service) 2. service file in systemd [Service] LimitCORE=infinity Environment="ASAN_OPTIONS=handle_segv=0:handle_abort=1:abort_on_error=1:disable_coredump=0"

[bash-script] get_info.sh print cpu allocation infomation of threads

1) way1 ps xH -o 'pid tid cmd comm pcpu psr' 2) way2 #!/bin/bash TMP_FILE=$(mktemp /tmp/abc-script.XXXXXX) echo ${TMP_FILE} ps xH -o 'pid tid cmd comm pcpu ' > ${TMP_FILE} function make_header() {   echo -n "$1"   echo " psr" } function make_values() {   echo -n "$1"   STATUS_FILE=/proc/${2}/task/${3}/status   if [ -f ${STATUS_FILE} ] ; then     CPU_SET=`cat ${STATUS_FILE}  |grep Cpus_allowed_list |awk ' { print $2 } '`   else     CPU_SET="None"   fi   echo " ${CPU_SET}" } let IDX=0 while IFS='' read -r line || [[ -n "$line" ]]; do    LINE_SEP=( $line )    MY_PID=${LINE_SEP[0]}    MY_TID=${LINE_SEP[1]}    if [ ${IDX} -eq 0 ]; then      SZ_HEADER=`make_header "$line"`      echo ${SZ_HEADER}    else      SZ_VALUES=`make_values "$line" ${MY_PID} ${MY_TID}`      echo ${SZ_VALUES}...

linux file system recovery

1. broken hdd disk backup  1) remote-server nc -v -l [port] > hdd_backup.img  2) equipment of broken hdd dd if=/dev/sda | nc -v [remote-server IP] [port]   ex)  1) remote-server nc -v -l 2222 > hdd_backup.img  2) equipment of broken hdd dd if=/dev/sda | nc -v 1.1.1.1 2222 2. use recovery tool  testdisk (http://www.cgsecurity.org/wiki/TestDisk_Download) 3. run fsck from img file  # losetup --offset 32256 /dev/loop2 harddrive.img  # fsck /dev/loop2  and again testdisk reference: https://major.io/2010/12/14/mounting-a-raw-partition-file-made-with-dd-or-dd_rescue-in-linux/ https://bbs.archlinux.org/viewtopic.php?id=136766