From: Jurriaan <thunder7@xs4all.nl>
To: Ian Stirling <linux-kernel@mauve.plus.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Debugging [binary] modules.
Date: Sun, 2 May 2004 12:10:46 +0200 [thread overview]
Message-ID: <20040502101046.GA5577@middle.of.nowhere> (raw)
In-Reply-To: <4093C5B8.5040806@mauve.plus.com>
From: Ian Stirling <linux-kernel@mauve.plus.com>
Date: Sat, May 01, 2004 at 04:43:52PM +0100
> Is there any tool that logs every access of a module to anything?
> Every memory or IO access, all calls, ...
> Ideally without requiring any alterations to the module binary, for the
> case when source isn't available.
You should be looking at Bochs, I think.
Kind regards,
Jurriaan
--
>"Unsolicited commercial electronic mail can be an important mechanism
> through which businesses advertise and attract customers in the online
> environment." (HR 718)
"Mugging can be an important mechanism through which the economically
disadvantaged gain and maintain the ability to pay taxes."
Reaction in news.admin.net-abuse.email by Alun Jones
Debian (Unstable) GNU/Linux 2.6.6-rc3-mm1 2x6062 bogomips 0.43 0.38
prev parent reply other threads:[~2004-05-02 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-01 15:43 Debugging [binary] modules Ian Stirling
2004-05-02 10:10 ` Jurriaan [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=20040502101046.GA5577@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=linux-kernel@mauve.plus.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox