Get backtrace when hook_block is triggered

Open
#1,324 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
reverse-engineering

Research direction

Start by locating the implementation and documentation for hook_block, then check whether the current API exposes a backtrace for the target process at the hook point. The issue is complete only when this capability is clearly available and covered by an appropriate test or documented as unsupported.

Written by the indexing model from the issue text.

Description

question

I want to get the backtrace of the target process at the hook point, does qiling currently have this feature?

Dominant language
Python
Stars
6.1k
Forks
798
Avg merge
1d 1h
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from qilingframework/qiling

All issues in qilingframework/qiling

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.