Context Navigation

Changes between Initial Version and Version 1 of Ticket #9858, comment 28

initial	v1
18	18	Anyway that suggestion is based on the assumption that knowing which variable [ 's contents] contains the corrupting buffer, is useful in identifying the code that is guilty of copying that contents into a wild place. Maybe one does not lead to the other and that assumption is wrong though..
19	19
20		(does kernelland have anything like the "watch-point" feature in userland debugger, to detect when a write ~~occurs into a memory area?~~)
	20	(does kernelland have anything like the "watch-point" feature in userland debugger, to detect when a write -- or as the case may be here, a read! -- occurs into a memory area?) (if yes we could point it to the memory area pointed by `fName`, see who reads its contents to write it elsewhere where it should not be)
21	21
	22