Re: Bug Report: Dereferencing a bad pointer

David Chandler (chandler@grammatech.com)
Thu, 08 Nov 2001 18:15:08 -0500


0xc0001000 hangs the same way that 0xc0000000 does. I have reproduced
this on a 2.4.9+UML kernel running in user-mode linux on top of a
Pentium-4 2.4.2-2(RedHat) host. 'top' says that 75% of CPU is going to
the system in that case also.

Please Cc: me on any replies.

David Chandler

--
_____
David L. Chandler.                              GrammaTech, Inc.
mailto:chandler@grammatech.com         http://www.grammatech.com

Brian Gerst wrote: > > David Chandler wrote: > > > > Debugging the offender, > > int main() { int k = (int *)0xc0000000; } > > is not very informative: single-stepping over the sole command just > > hangs, and you have to press Control-C to interrupt gdb, at which point > > you can single-step right into the same problem again. > > > > When the program hangs, 'top' says that the CPU is fully utilized and > > the system is spending 80% of its time in the kernel and 20% in the > > offending process. > > > > Have you not been able to duplicate it on a 2.4 kernel on x86? If not, > > please tell me which 2.4 kernel correctly seg faults. > > How about address 0xc0001000? I have been unable to reproduce this on a > PII running 2.4.9, and an Athlon running 2.4.14. > > -- > > Brian Gerst - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/