Re: Unable to find vma for addr 0xc39fff98

Uncle George (gatgul@voicenet.com)
Sun, 28 Jun 1998 08:03:28 -0400

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Topi Miettinen: "/proc/kmsg oddness, patch"
Previous message: B. James Phillippe: "{b,}zImage - non-x86 (was Re: bzImage and zImage)"
Maybe in reply to: Felix von Leitner: "Unable to find vma for addr 0xc39fff98"

u should be careful, VMA errors ( for me )also happens on a gdb restart.
The # of vma errors, just dont seem to match up the # of leftover
breakpoints i had in the debug session.
oh well
gat

Richard Henderson wrote:

> On Sat, Jun 27, 1998 at 09:24:09PM +0200, Felix von Leitner wrote:
> > What does the above message mean and what can I do about it?
>
> It is a debugging message that has for some reason been left in.
> It means gdb poked process memory that did not exist. As that
> is a perfectly acceptible thing for gdb to be doing.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

Next message: Topi Miettinen: "/proc/kmsg oddness, patch"
Previous message: B. James Phillippe: "{b,}zImage - non-x86 (was Re: bzImage and zImage)"
Maybe in reply to: Felix von Leitner: "Unable to find vma for addr 0xc39fff98"