Silence using uninitialized value

Поиск
Список
Период
Сортировка
От Ranier Vilela
Тема Silence using uninitialized value
Дата
Msg-id CAEudQApZnTYftuM-opLARSFOQ2uivxcu894xH+KXj2t4H-eouw@mail.gmail.com
обсуждение исходный текст
Список pgsql-hackers
Hi.

Per Coverity.

Coverity has new report about tablecmds.c and tablespace.c

tablecmds.c:
CID 1608920: (#1 of 1): Uninitialized scalar variable (UNINIT)
6. uninit_use_in_call: Using uninitialized value *repl_val when calling heap_modify_tuple.


CID 1608899: (#1 of 1): Uninitialized scalar variable (UNINIT)
16. uninit_use_in_call: Using uninitialized value *repl_val when calling heap_modify_tuple.


tablespace.c:
CID 1608898: (#1 of 1): Uninitialized scalar variable (UNINIT)
6. uninit_use_in_call: Using uninitialized value *repl_val when calling heap_modify_tuple.


I don't think that is a bug.
But really the uninitialized value is read here:

3. read_value: Reading value replValues[attoff].
1242                        values[attoff] = replValues[attoff];
1243                        isnull[attoff] = replIsnull[attoff];
1244                }

There a common pattern in the source code:

value = (Datum) 0;
null = true;

So I believe it is worth changing to the standard used.

patch attached.

best regards,
Ranier Vilela

Вложения

В списке pgsql-hackers по дате отправления: