Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backtracing Async functions (+Task return type) #535

Open
HomerSimpson00007 opened this issue Aug 11, 2024 · 2 comments
Open

Backtracing Async functions (+Task return type) #535

HomerSimpson00007 opened this issue Aug 11, 2024 · 2 comments
Labels
question A question about anything

Comments

@HomerSimpson00007
Copy link

Was using the Backtracer (Works very well!), But entountered a problem, when trying to trace an async function, the backtrace result is always the same, all functions originate from MoveNext function (Due to the Statemachine), example:
0x06301eb8+0x000 TBetterBinaryProtocol::WriteBinaryAsync 0x062ccf98+0x094 Thrift.Protocol.TProtocol.<WriteStringAsync>d__39::MoveNext

Any other idea to backtrace such functions?

@commonuserlol
Copy link

it's good idea to share your code. I guess you need backtrace the WriteStringAsync function, or use tracer on target class(es)

@vfsfitvnm vfsfitvnm added the question A question about anything label Aug 24, 2024
@vfsfitvnm
Copy link
Owner

Any other idea to backtrace such functions?

No clue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question A question about anything
Projects
None yet
Development

No branches or pull requests

3 participants