TOP Contributors

  1. MIKROE (2784 codes)
  2. Alcides Ramos (405 codes)
  3. Shawon Shahryiar (307 codes)
  4. jm_palomino (133 codes)
  5. Bugz Bensce (97 codes)
  6. S P (73 codes)
  7. dany (71 codes)
  8. MikroBUS.NET Team (35 codes)
  9. NART SCHINACKOW (34 codes)
  10. Armstrong Subero (27 codes)

Most Downloaded

  1. Timer Calculator (141569 times)
  2. FAT32 Library (74513 times)
  3. Network Ethernet Library (59053 times)
  4. USB Device Library (49044 times)
  5. Network WiFi Library (44811 times)
  6. FT800 Library (44376 times)
  7. GSM click (31066 times)
  8. mikroSDK (29922 times)
  9. microSD click (27486 times)
  10. PID Library (27484 times)
Libstock prefers package manager

Package Manager

We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]

< Back
Project

Tool: Function Calls Display

Rating:

10

Author: dany

Last Updated: 2020-03-13

Package Version: 1.0.2.1

Category: Other Codes

Downloaded: 990 times

Not followed.

License: MIT license  

Shows the function calls of the project in a number of views (a.o. graphical tree).

For mP, mC and mB for PIC and dsPIC.

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "Tool: Function Calls Display" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "Tool: Function Calls Display" changes.

Do you want to report abuse regarding "Tool: Function Calls Display".

  • Information
  • Comments (4)
DOWNLOAD LINK RELATED COMPILER CONTAINS
Other Compiler
  • lib
  • src
  • exa
  • hlp
  • hex
  • sch
  • pcb
  • doc

Project Blog

For mP, mC and mB for PIC and dsPIC.

* Shows the function calls (1 level deep) of the project in a number of views:

- which functions use which other functions (-1- left main window)

- which functions are used by other functions (-2- right main window)

* Additionally the following info is given:

- the (deepest) stack call level, the needed stack depth and the call frequency of a function (3)

- the deeptest call stack (the names of its subsequent called functions) of a function (4)

- the full call stack (the names of its subsequent called functions) of a function (5)

(1), (2) and (3): see ScreenShot

(4) and (5): see ScreenShot

- Selecting a function in one view shows all its occurences in the other view.

- Double clicking a function goes "down" in the call stack in the "uses" view, and "up" in the call stack in the "is used by" view.

- Right clicking a function shows its call stacks in a separate screen.


* The call tree of the last selected function in one of both main windows can be shown graphically (and saved to a file).

* The call depth shown can be limited in the graphical view. One can click one of the procedures on the screen to see its caller tree, and go to previous procedures selected via the history. Single functions (and their callees) or all functions from specific libraries can be ingored in the graphicall call tree.


* The inverse graphical tree (which routines do call the selected one) is also provided.


* The Project's Module tree (which modules/units use other modules/units) and a Module's Routine tree (the call graph of all routines inside a module/unit) are also present.


Keep in mind that all info that you see is that of the current project. This means e.g. that unused procedures are not shown!

So: always compile the project before tool usage, the tool needs the listfile and the callertable.

The tool is to be started up from within the IDE, it can not be used stand alone.

Tool settings in the IDE (Options-Tools).

Screenshot (1), (2), and (3)

Screenshot (1), (2), and (3)

Screenshot (1), (2), and (3)

View full image
Screenshot (4) and (5)

Screenshot (4) and (5)

Screenshot (4) and (5)

View full image
Call tree

Call tree

Call tree

View full image
Inverse graphical tree

Inverse graphical tree

Inverse graph tree

View full image
Project's Module tree

Project's Module tree

Project's Module tree

View full image
Module's routine tree

Module's routine tree

Module's routine tree

View full image
Tool settings in the IDE (Options-Tools).

Tool settings in the IDE (Options-Tools).

Tool settings in the IDE (Options-Tools).

View full image

------------------------------------------------------------------------------------------------------------------------------------------
Version 10.2: Problems with finding PIC32 interrupt routines solved.

------------------------------------------------------------------------------------------------------------------------------------------
Version 10.4: Problem for P18 solved.

Version 11.0: Also '*.inc' files including code are recognised now.

ALSO FROM THIS AUTHOR

LCD

11

* 2 (alternative) libs to drive LCD's (4 bits connections): - One lib specific for 2x16, - one more generic (upto 4 rows, 16-20 chars per row). * A library to drive LCD via I2c (PCF2116 based, 1 to 4 rows, 12 or 24 chars per row * A library to drive standard LCD's via I2c * A library to drive standard LCD's via SPI.

[Learn More]

I2c non blocking

10

Replacement routines for I2c1_Rd and I2c1_Wr but here with timeout, so no blocking any more when a device one tries to access is not present. The mE I2c library is still needed for the remaining I2c routines. Implemented also the code for controllers with 2 I2c's (e.g. P18F27K40).

[Learn More]

Tool: Basic Source code Formatter

5

This tool is a simple mikroBasic source code formatter, mainly making correct and readable code indentation.

[Learn More]