* Debugging [binary] modules.
@ 2004-05-01 15:43 Ian Stirling
2004-05-02 10:10 ` Jurriaan
0 siblings, 1 reply; 2+ messages in thread
From: Ian Stirling @ 2004-05-01 15:43 UTC (permalink / raw)
To: linux-kernel
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Debugging [binary] modules.
2004-05-01 15:43 Debugging [binary] modules Ian Stirling
@ 2004-05-02 10:10 ` Jurriaan
0 siblings, 0 replies; 2+ messages in thread
From: Jurriaan @ 2004-05-02 10:10 UTC (permalink / raw)
To: Ian Stirling; +Cc: linux-kernel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-05-02 10:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-05-01 15:43 Debugging [binary] modules Ian Stirling
2004-05-02 10:10 ` Jurriaan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox