[lkml]   [2001]   [Nov]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Bug Report: Dereferencing a bad pointer
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.

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
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:13    [W:0.098 / U:0.088 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site