Lines Matching refs:was

80 	modifies memory that was tracked by kmemcheck, the result is an
264 If your kernel was compiled with CONFIG_DEBUG_INFO=y, then all we have to do
278 In this case, the flag was very important, because otherwise, it would only
297 Since this was a read (kmemcheck usually warns about reads only, though it can
298 warn about writes to unallocated or freed memory as well), it was probably the
300 of calls, we move upwards to see where "from" was allocated or initialized,
322 variable "first" was found on a list -- passed in as the second argument to
324 where the item on "list" was allocated or initialized. We move to line 410:
463 And, you might remember, it was a memcpy() on &first->info that caused the
492 uninitialized memory was located, we have to look at the disassembly. For
528 that the uninitialized value was encountered at 4 * (0xc - 0x9) = 12 bytes
531 We can now try to figure out which field of the "struct siginfo" that was not
610 was not tracked. We can dig a little deeper into the stack trace from above:
633 was all about.
718 fault handler notices that the page was in fact only hidden, and so it calls