algoDEA
  • algoDEA - Algorand IntelliJ Plugin
  • Overview
  • Installation using JetBrains Plugin Repository
  • Installation - Manual
  • Algorand Node Configuration
  • Account Management
  • Algorand Project Structure
  • Compile TEAL Program
  • Import an existing project
  • Variables/Placeholders in TEAL program
  • Stateful Smart Contract
    • Create Project - Stateful Smart Contract
    • Stateful Smart Contract - Deploy
  • Multiple Stateful Smart Contract in a Project
  • Stateless Smart Contract
    • Create Project - Stateless Smart Contract
    • Stateless Smart Contract - Delegated Signature
  • Stateless Smart Contract - Contract Account
  • Algorand Standard Assets
    • Create, Manage & Transfer
  • Atomic Transfer
    • Create Atomic Transfer
  • Dry Run
    • Dry Run Stateful / Stateless Contract Call
    • Dry Run - Atomic Transfer
  • PyTeal
    • Configure Python SDK and PyTeal
  • Create PyTeal file
  • Create or Configure a Stateful Contract with PyTeal Programs
  • Compile PyTeal File
  • Debugger Support (Beta)
    • Overview
    • Debugger Configuration
    • Debug Stateless Contract
    • Debug Stateful Smart Contract
    • Debug Stateful Contract using Dry Run Dump file
    • Debug Atomic Transfer
  • Debug Atomic Transfer using Dry Run Dump file
Powered by GitBook
On this page

Was this helpful?

  1. Debugger Support (Beta)

Overview

Supported Since : 0.7.0-Beta1

The plugin provides integration with "tealdbg" to provide debugging support for TEAL smart contracts. Currently, the debugger support is available for the followings:

  • Stateless Smart Contract

  • Stateful Smart Contract

  • Atomic Transfer

When debugger option is chosen for a smart contract transaction, the following steps are done by the plugin :-

  • If stateful smart contract, it creates the debugger context (Dry run dump) file

  • Starts tealdbg with TEAL source file and dry run dump file

  • Finds Google Chrome installation and automatically opens the browser for debugging (If automatic detection is enabled)

Alternatively, developer can directly use the dry run dump file and debug. The steps are as follows :-

  • Create debugger context (dry run dump) file from the supported transaction UI

  • Right click on the dry run dump file and select "Start TEAL debugger" to start the debugger.

Note: IDE automatically finds the Chrome executable and opens it. But this feature has only been tested on Mac OS and Windows. For Linux, you may need to configure the Chrome executable path in the "Debugger Configuration" UI.

PreviousCompile PyTeal FileNextDebugger Configuration

Last updated 3 years ago

Was this helpful?