Mulyadi Santosa wrote:
On Sun, Jul 27, 2008 at 9:29 AM, Peter Teoh <[EMAIL PROTECTED]> wrote:
Just want to share this.
First, at:
http://tuxology.net/lectures/crash-and-burn-writing-linux-application-fault-handlers/
At page 6, is the common practise of capturing the stacktrace,
whenever error occurred. But this is actually wrong, and will give
rise to race condition.
Damn, Gilad moves faster than me! Actually, I was experimenting with
relatively same thing...but my original goal is to show to newbies how
Xen/KVM/etc intercept memory access and redirect the accessor to
another address. The work is incomplete though...
regards,
Mulyadi.
You mean like the stack piercing attack for Windows callbacks in the
messaging subsystem?
...
That is quite possibly the geekiest thing I've ever written... I'm not
sure if I should feel good or bad about that ;)
Anyways, are you working on it with libvert? I've been geeking out over
that and I'm hoping to get something going on the dual quad core xeons
at work ;) Unfortunately, it only has 2 GB RAM since FB-DIMMs are still
expensive.
