PERFORCE change 132936 for review

John Birrell jb at FreeBSD.org
Wed Jan 9 17:49:40 PST 2008


http://perforce.freebsd.org/chv.cgi?CH=132936

Change 132936 by jb at jb_freebsd1 on 2008/01/10 01:49:17

	Enable the toxic range additions.
	
	Now that we have a DTrace probe safe printf() call (enabled if built
	with DEBUG mode enabled), lets log attempts to write to toxic addresses.

Affected files ...

.. //depot/projects/dtrace/src/sys/contrib/opensolaris/uts/common/dtrace/dtrace.c#15 edit

Differences ...

==== //depot/projects/dtrace/src/sys/contrib/opensolaris/uts/common/dtrace/dtrace.c#15 (text) ====

@@ -481,6 +481,7 @@
 									\
 		if (addr + size <= dtrace_toxrange[i].dtt_base)		\
 			continue;					\
+dtrace_debug_printf("%s: 0x%lx <= addr 0x%lx <= 0x%lx\n", __func__,(u_long) dtrace_toxrange[i].dtt_base,(u_long) addr,(u_long) dtrace_toxrange[i].dtt_limit); \
 									\
 		/*							\
 		 * This address falls within a toxic region; return 0.	\
@@ -14559,8 +14560,6 @@
 static void
 dtrace_toxrange_add(uintptr_t base, uintptr_t limit)
 {
-printf("%s(%d): DOODAD\n",__func__,__LINE__);
-#ifdef DOODAD
 	if (dtrace_toxranges >= dtrace_toxranges_max) {
 		int osize, nsize;
 		dtrace_toxrange_t *range;
@@ -14593,7 +14592,6 @@
 	dtrace_toxrange[dtrace_toxranges].dtt_base = base;
 	dtrace_toxrange[dtrace_toxranges].dtt_limit = limit;
 	dtrace_toxranges++;
-#endif
 }
 
 /*


More information about the p4-projects mailing list