On Tue, 2014-01-21 at 06:32 +0000, Jun Yuan wrote: > Sorry for repeated post if I have post more than once......I did not receive > the confirmation for the first time post > > Hello, > > Thanks for the constant help! I have one more question now... > > So far valgrind function wrapper only supports word type for arguments and > return types. It is fine when encountering larger than words types like float > or double I can always represent double as two words, but how about arguments > with finer type like byte(8 bits) or short(16 bit)? If I use word to > represent them will it cause any problem such as corrupting the stack upon > function returning?
I do not see why byte or short granularity args should cause a problem as the macros are doing a cast to unsigned long when passing the arg values to the wrapper function. The wrapper return value is cast to the type of the result variable. This should all work ok. Philippe ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
