From: empty <idabsentgi@gmail.com>
To: gdb@sourceware.org
Subject: Stack trace during binary file execution
Date: Sun, 15 Jan 2023 03:09:25 +0300 [thread overview]
Message-ID: <P33IOR.7JPIYWJ89SJ32@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
Hello. I apologize for my English, which I do not know =). This text is
machine translation.
I am interested in the possibility of implementing function call
tracing. I found a similar utility - strace, which provides a trace of
system calls. But this system call tracing is limited, allowing you to
track user functions only indirectly. Therefore, the question is: is it
possible to implement such a utility? If possible, are there any
restrictions for this?
The question is not really about pve, but I don't know where else to
get information on this issue (I didn't get an answer on stackoverflow).
To study the topic, I studied a little the logic of strace, which works
through ptrace, but I'm not quite sure yet.
If I am writing in the wrong place, then please correct who I can
contact for a little information.
reply other threads:[~2023-01-15 0:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=P33IOR.7JPIYWJ89SJ32@gmail.com \
--to=idabsentgi@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).