What's the difference?
When using the debug ON, what messages can I get?
How can I build a non-debug ON? just use the non-debug on-closed-bins?
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Hi,
On 07/05/07 10:17, ?? Tao Jie wrote:
> What's the difference?
Debug bits are compiled with DEBUG defined (-DDEBUG on cc cmdline etc).
So any code that is bracketed by a #ifdef DEBUG ... #endif becomes
active. This brings additional levels of debug and checking to
life, eg in the sample code:
[ opensolaris-code would have been a better place, I've set replys to go
there ]
陶捷 Tao Jie wrote:
> What's the difference?
The debug kernel is built with DEBUG=1 defined so that code behind an
#ifdef DEBUG is enabled.
> When using the debug ON, what messages can I get?
Debug ones :-)
> How
I see~ You're all warmhearted, thanks all :)
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
btw, How can I determine whether the ON is a debug version or a
non-debug version, if it is not built by myself and I only have the
"Install.i86pc.tar" tarball?
1, Before I bootup this ON, what could I do?
&
2, When this ON is running, what could I do?
Thanks :)
Regards
TJ
2007/7/5, Gavin Malt
Hi Tao Jie.
While booted, you can check for existence of variables declared only if
DEBUG is set on.
You can use the following command:
/usr/ccs/bin/nm /dev/ksyms | grep
Using mdb, you can also check the value of variables which are different
depending on DEBUG. For example, kmem_flags
