All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-c-programming@vger.kernel.org, linux-assembly@vger.kernel.org
Subject: Re: monitoring code while executing.
Date: Mon, 22 Nov 2004 20:35:33 +0100	[thread overview]
Message-ID: <20041122193533.GP26791@lug-owl.de> (raw)
In-Reply-To: <20041122182459.60354.qmail@web51903.mail.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 879 bytes --]

On Mon, 2004-11-22 10:24:59 -0800, A M <alim1993@yahoo.com>
wrote in message <20041122182459.60354.qmail@web51903.mail.yahoo.com>:
> Can anybody think of a method in which one process can
> view (monitor, read) the instructions of another
> process while it is running (one process see
> instruction of another process while they get fetched
> to be executed)? Is it possible with threads instead
> of processes? 

Any debugger (like gdb) or system/library call tracer (strace, ltrace)
does this using the ptrace system call.

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-11-22 19:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-22 18:24 monitoring code while executing A M
2004-11-22 19:35 ` Jan-Benedict Glaw [this message]
2004-11-22 21:17   ` Daniel Souza
  -- strict thread matches above, loose matches on Subject: below --
2004-11-22 21:15 A M
2004-11-23  5:50 ` Jan-Benedict Glaw

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=20041122193533.GP26791@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-assembly@vger.kernel.org \
    --cc=linux-c-programming@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.