"Fedor V. Sergeev" wrote: > On Sat, Mar 15, 2008 at 04:47:25PM +0100, Roland Mainz wrote: > > Does anyone know tools to track down problems caused by uninitalised > > global or stack variables except dbx's "check -access" functionality > > (which doesn't work in B84) which work in Solaris 11 ? > > > > BTW: Did anyone thought about adding compiler options yet to initalise > > "uninitalised" variables with a fixed byte sequence > > We have plans for finalizing -xcheck=init_local implementation in C/C++ > compilers > in upcoming release. It is not yet available as a first-class option, as per > SS12patch or latest express release.
Could you please add a small RFE to add a new option to specify a byte sequence used to init "uninitalised" variables, e.g. -xinit_uninitalised_local=0xDEADBEEF (which would init all uninitalised local variable memory with the repeated (up to |sizeof(variable)| bytes) byte sequence 0xDEADBEEF (specifying -xinit_uninitalised_local=0x00 would fill all uninitalised local variable memory with the zeros etc. etc.)). The idea is not only to report uninitalised variables, the idea is to get predictable behaviour for debugging (or at least track down whether the problem is actualyl related to such a variable or something else). ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;)
