linux-trace-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: alexandre.ferrieux@orange.com
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-users@vger.kernel.org
Subject: Re: Ftrace, KASLR and gdb
Date: Mon, 13 May 2024 20:26:01 +0200	[thread overview]
Message-ID: <c6bc4ca5-0ead-4954-89ce-55a44ac766f8@orange.com> (raw)
In-Reply-To: <20240513122522.5c80ab0f@rorschach.local.home>



On 13/05/2024 18:25, Steven Rostedt wrote:
> 
> Ah, so you are running gdb on the live kernel.

Yep - sorry I didn't make it clear in the first place :)

>> So, is there currently another method to reach the same effect ?
> 
> Besides kgdb (usually another machine connected to the live kernel),
> this is probably the only way to do what you want.
Ok, thank you for the info.

One reason I'm not using kgdb, beside the obvious pain it is to set up a second 
machine with the appropriate link... is the spirit of ftrace itself: no need for 
breakpoints when you have a nearly-zero-overhead, flexible logger.

And learning from the "live beast" is a 1000x speedup wrt reading the source. 
Learning the Linux Kernel, as open as its source may be, largely remains a 
reverse-engineering operation. With Ftrace, Pahole, and Gdb, one can dig 
*anywhere*. My reasserted kudos for making this possible !

-Alex



____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

      reply	other threads:[~2024-05-13 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-09 12:44 Ftrace, KASLR and gdb alexandre.ferrieux
2024-05-10 18:12 ` Steven Rostedt
2024-05-11 22:44   ` alexandre.ferrieux
2024-05-13 16:25     ` Steven Rostedt
2024-05-13 18:26       ` alexandre.ferrieux [this message]

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=c6bc4ca5-0ead-4954-89ce-55a44ac766f8@orange.com \
    --to=alexandre.ferrieux@orange.com \
    --cc=linux-trace-users@vger.kernel.org \
    --cc=rostedt@goodmis.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 NNTP newsgroup(s).