Don Zickus <[email protected]> writes:
> >
> > Odd. I wonder if I'm missing a serializing instruction somewhere,
> > to ensure the effects of ``self modifying code'' aren't a problem.
> > As I read Intels Documentation if you have a jump before you get
> > to the code there shouldn't be a problem.
> >
> > Still that doesn't really explain bytes_out.
> >
Sounds nasty.
>
> So I narrowed down the problem but it isn't obvious to me why this problem
> exists. Basically, even though bytes_out is supposed to be initialized to
> 0, it becomes -1 before entering decompress_kernel(). Of course, the
> fallout is in flush_window() bytes_out wounds up being one less than
> outcnt and hence my original problem.
>
> Any thoughts on how to debug where this could be getting corrupted?
Use a simulator (hopefully you can reproduce it in there) like qemu
or AMD SimNow and set a watch point on the address?
Or try to find someone who has a Intel target probe to help you out.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
