|
From: Nicholas N. <nj...@ca...> - 2004-04-17 11:33:17
|
On Sat, 17 Apr 2004, Banibrata Dutta wrote: > e.g. > ==4654== Address 0x3D455F91 is 41 bytes inside a block of size 43 alloc'd > ==4654== at 0x3C020C59: __builtin_vec_new (vg_replace_malloc.c:116) > ==4654== by 0x804C7CD: NC_PttUdpSmsMsg::setParams(SmsBearerData *, > SmsOriginalOriginatingAddress *) (NC_PttUdpSmsMsg.C:191) > ==4654== by 0x804B499: NC_CdmaProvider::processSMDPP(char *, int, int, > tc_address_struct, tc_address_struct, int, pair<int, int> *) > (NC_CdmaProvider.C:272) > ==4654== by 0x804E99E: NC_TcapManagerImpl::decodeComponent(int, int, > tc_primitive_type, tc_address_struct, tc_address_struct, tc_control_c) > (NC_TcapManagerImpl.C:708) > ==4654== > > so, what is the meaning of this error ? when/how can this be caused ? See section 3.3.5 of the manual. (eveloper.kde.org/~sewardj/docs-2.0.0/mc_main.html#mc-top) > also, if i have a code block like... > > { > int x; > int y; > > func(&x); > > y=x+2; > } > > does it flag an error, saying 'x' is not initialized while being used to > determine value of 'y'. note that in my case func() is supposed to modify > 'x'. It won't complain here. It might complain later, if y is used in a way that will affect the program's behaviour. It only complains if an uninitialised value is used in a way that will affect the program's execution, eg. as an address, or an input to a system call, or in a conditional jump. See section 3.5.1 of the manual for an explanation why. N |