free(95b724d) bad block. (memtop = 0x96e9800 membot = 0x95ae000)
free(8de324d) bad block. (memtop = 0x8f15800 membot = 0x8dda000)
free(9a8924d) bad block. (memtop = 0x9bbb800 membot = 0x9a80000)
So the same thing happens each time, but different information....
On Thu, Apr 19, 2012 at 5:41 PM, Michal Jaegermann <michal@xxxxxxxxxxxx> wrote:
On Thu, Apr 19, 2012 at 04:48:54PM -0400, Brian Johnson wrote:You are right that in such case hardware problems look like a remote
>
> What's odd, though, and makes it seem unlikely it's a disk issue is, this
> is happening on 2 different machines
possibility. Only that error you are quoting seems to be at least
weird. Is it really the same on both machines? Is it consistent on
different attempts on the same machine? That could be an effect of
something scribbling where it is not supposed to and messing memory. It
could be "interesting" to find. You have gdb and 'screen-debug' and
possibly you can get something with these.
Michal
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
