From: Oleg Nesterov <oleg@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
utrace-devel@redhat.com, archer@sourceware.org
Subject: Re: gdbstub initial code, v7
Date: Fri, 03 Sep 2010 23:00:00 -0000 [thread overview]
Message-ID: <20100903225738.GB8917@redhat.com> (raw)
In-Reply-To: <y0m62ymzzbd.fsf@fche.csb>
On 09/03, Frank Ch. Eigler wrote:
>
> Oleg Nesterov <oleg@redhat.com> writes:
>
> > [...] To the point, I had to add printk's to utrace.c to understand
> > what is wrong. Hopefully tomorrow.
>
> You might wish to try out systemtap for such purposes. It's easy to
> insert printk-like tracing at almost any point; monitor variables for
> changes, pretty-print structs, etc.
Probably I should try the new versions...
Last time I tried systemtap more than year ago. It didn't work for me
without the "properly installed" kernel/etc which I don't have. And,
I doubt I can insert the probe at the needed line without DEBUG_INFO.
> No recompilation/reboot.
CONFIG_KPROBE ;)
But anyway I agree, systemtap is the great tool.
Oleg.
prev parent reply other threads:[~2010-09-03 23:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 19:02 Oleg Nesterov
2010-08-30 19:20 ` Jan Kratochvil
2010-08-31 7:21 ` Jan Kratochvil
2010-09-02 20:09 ` Oleg Nesterov
2010-09-03 6:40 ` Jan Kratochvil
2010-09-03 19:59 ` Roland McGrath
2010-09-03 20:03 ` Jan Kratochvil
2010-09-03 20:10 ` Roland McGrath
2010-09-03 23:13 ` Oleg Nesterov
2010-09-10 10:15 ` Roland McGrath
2010-09-10 18:32 ` Oleg Nesterov
2010-09-10 19:06 ` Roland McGrath
2010-09-10 19:23 ` Oleg Nesterov
2010-10-13 7:23 ` Roland McGrath
2010-10-15 14:32 ` Oleg Nesterov
2010-09-03 14:17 ` Frank Ch. Eigler
2010-09-03 23:00 ` Oleg Nesterov [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=20100903225738.GB8917@redhat.com \
--to=oleg@redhat.com \
--cc=archer@sourceware.org \
--cc=fche@redhat.com \
--cc=jan.kratochvil@redhat.com \
--cc=utrace-devel@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).