Hi All,
I'm trying to understand what valgrind 3.5 is complaining about in the
only db_if.c item in the latest valgrind report.
==46991== Conditional jump or move depends on uninitialised value(s)
==46991== at 0x88B1386: sortReadersWriters (db_if.c:7036)
==46991== by 0x88B1CA2: add_procs_from_debug_section_to_db
(db_if.c:7219)
...
The code at db_if.c:7036 is in red below:
for (i=0; i < count2; i += 2) {
/* the instance name will have a subscript, compare name up to the
subscript */
if (!strncmp(list2[i+1], name, nameLen) && list2[i+1][nameLen] ==
'[') {
int idx;
int length;
/* compute index of instance, ignore the instance array itself
*/
int ss = sscanf(list2[i+1]+nameLen,"[%d]%n", &idx, &length);
if ((ss == 1) && (length == strlen(list2[i+1])-nameLen) ) {
It appears that everything used in that line is set. Might valgrind not
recognize the values set to idx and length in the call to sscanf()?
- Osman
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
