lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: "Danter, Richard via lttng-dev" <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] Adding a simple "look here" event to the trace
Date: Fri, 8 Sep 2023 10:56:16 +0000	[thread overview]
Message-ID: <661596f68dcda5a1aa87cd5faa4d5f6c5937728e.camel@windriver.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 944 bytes --]

Hi all,

I am investigating an issue that takes some time to reproduce. Finding
the right point in the logs is therefore very difficult.

Since I can detect when the issue happens in the kernel I would like to
be able to emit an event into the trace that I can then search for in
Trace Compass of through Babeltrace. So basically a kind of flag that
says "look here". That way I can jump right to the problem and then
look backwards from there to see what happened just before.

I have looked at the docs for how to add a trace point, but it seems
pretty complicated. I may have missed something though, so I wonder if
there is a trivial way to add such a flag to the log? Up to now I just
put a printk() in which helps, but would still be nicer to have
something directly in the log.

If there isn't such a thing already, then would it be a reasonable
enhancement request to be able to add such a feature?

Thanks
Rich


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

             reply	other threads:[~2023-09-08 11:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08 10:56 Danter, Richard via lttng-dev [this message]
2023-09-27 11:54 ` [lttng-dev] Adding a simple "look here" event to the trace Erica Bugden via lttng-dev

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=661596f68dcda5a1aa87cd5faa4d5f6c5937728e.camel@windriver.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=Richard.Danter@windriver.com \
    /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).