Bullish Global (20240256428). SYSTEM AND METHOD FOR INTERACTIVELY DEBUGGING WEBASSEMBLY CODE simplified abstract

From WikiPatents
Jump to navigation Jump to search

SYSTEM AND METHOD FOR INTERACTIVELY DEBUGGING WEBASSEMBLY CODE

Organization Name

Bullish Global

Inventor(s)

Huang-Ming Huang of St. Louis MO (US)

Qing Yang of Williamsburg VA (US)

Santhosh Nagappa Kumaraswamy of Rocky Point NY (US)

Jiaen Du of Hong Kong (CN)

Kevin Heifner of Pensacola FL (US)

Zhiqiang (Eric) Ma of Hong Kong (CN)

Farhad Shahabi of Ashburn VA (US)

Jingjun Zhao of Blacksburg VA (US)

Keke Li of Freemont CA (US)

Victor Sanchez Camacho of Austin TX (US)

Patrick Raphael of Ashburn VA (US)

Aaron Fu of Hong Kong (CN)

Mothusi Sean Majinda of Hong Kong (CN)

SYSTEM AND METHOD FOR INTERACTIVELY DEBUGGING WEBASSEMBLY CODE - A simplified explanation of the abstract

This abstract first appeared for US patent application 20240256428 titled 'SYSTEM AND METHOD FOR INTERACTIVELY DEBUGGING WEBASSEMBLY CODE

The patent application relates to the interactive debugging of non-native code within native executables, specifically focusing on WebAssembly (WASM) code. By converting source smart contract code into a native binary shared library, the code can be loaded by a blockchain executable for execution, with control passed to the shared library. A debugger can then be attached to the host executable to step through the smart contract code.

  • Interactive debugging of non-native code inside native executables
  • Conversion of source smart contract code into a native binary shared library
  • Loading shared libraries by blockchain executables for execution
  • Attaching a debugger to the host executable to step through smart contract code
  • Generating execution trace information for smart contracts from non-native code

Potential Applications: - Debugging and optimizing smart contract code in blockchain applications - Enhancing performance analysis of smart contracts compared to native execution - Facilitating the development and deployment of complex blockchain applications

Problems Solved: - Identifying erroneous execution logic in non-native code - Improving performance issues in smart contract execution - Enabling interactive debugging of shared libraries within blockchains

Benefits: - Enhanced debugging capabilities for developers working with non-native code - Improved performance optimization for smart contracts - Streamlined development processes for blockchain applications

Commercial Applications: Title: "Enhanced Debugging and Performance Optimization for Blockchain Applications" This technology can be utilized by blockchain development companies to streamline the debugging and optimization process for smart contracts, leading to more efficient and reliable blockchain applications. It can also be valuable for companies looking to improve the performance of their blockchain solutions.

Questions about Interactive Debugging of Non-Native Code in Native Executables: 1. How does the conversion of source smart contract code into a native binary shared library benefit developers? By converting the code into a shared library, developers can easily load and debug the code within native executables, improving the efficiency of the debugging process.

2. What are the key advantages of using a debugger to step through smart contract code in blockchain applications? Using a debugger allows developers to identify and resolve errors in the code, leading to more reliable and optimized smart contracts.


Original Abstract Submitted

embodiments relate to interactively debugging non-native code inside native executables to identify erroneous execution logic and/or performance issues. the non-native code can be webassembly (wasm) code. source smart contract code can be converted into a native binary in a format of a shared library. the shared library can be loaded by a blockchain executable when ready to load the smart contract for execution, and execution control can be passed to the shared library. a debugger can be attached to the host executable and single step through the smart contract code invoked. embodiments relate to enabling interactive debugging of code as shared libraries (.so files) inside blockchains and native executables and/or generating execution trace information for smart contracts from non-native code without modifying its execution logic and/or generating relative performance information comparing smart contract execution in blockchains as non-native code with native execution as shared libraries to establish performance benchmarks.