Project

General

Profile

Actions

Bug #1670

closed

Modbus compiler warnings on Fedora 23

Added by Peter Manev over 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

When compiling 3.0RC3 from source on Fedora 23 -

[root@localhost suricata-3.0RC3]# uname -a
Linux localhost.localdomain 4.2.7-300.fc23.x86_64 #1 SMP Wed Dec 9 22:28:30 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

the following warnings are present about modbus:

  CC       app-layer-modbus.o
app-layer-modbus.c: In function ‘ModbusParseWriteRequest’:
app-layer-modbus.c:736:31: warning: ‘byte’ may be used uninitialized in this function [-Wmaybe-uninitialized]
                 tx->data[i] = (uint16_t) byte;
                               ^
app-layer-modbus.c: In function ‘ModbusParseResponse’:
app-layer-modbus.c:614:24: warning: ‘count’ may be used uninitialized in this function [-Wmaybe-uninitialized]
                 (count != (2 * (tx->read.quantity))))
                        ^
app-layer-modbus.c:599:13: note: ‘count’ was declared here
     uint8_t count;
             ^
app-layer-modbus.c:1164:24: warning: ‘mei’ may be used uninitialized in this function [-Wmaybe-uninitialized]
                     if (mei != tx->mei)
                        ^
app-layer-modbus.c:1121:49: note: ‘mei’ was declared here
     uint8_t     count, error = FALSE, function, mei;
                                                 ^
app-layer-modbus.c:1156:21: warning: ‘count’ may be used uninitialized in this function [-Wmaybe-uninitialized]
                     ModbusCheckHeaderLength(modbus, tx->length, 2 + count);
                     ^
app-layer-modbus.c:1121:17: note: ‘count’ was declared here
     uint8_t     count, error = FALSE, function, mei;
                 ^
app-layer-modbus.c:499:5: warning: ‘exception’ may be used uninitialized in this function [-Wmaybe-uninitialized]
     switch (exception) {
     ^
app-layer-modbus.c:493:13: note: ‘exception’ was declared here
     uint8_t exception;
             ^
app-layer-modbus.c:1138:13: warning: ‘function’ may be used uninitialized in this function [-Wmaybe-uninitialized]
             switch(function) {
             ^
app-layer-modbus.c:1121:39: note: ‘function’ was declared here
     uint8_t     count, error = FALSE, function, mei;
                                       ^
app-layer-modbus.c: In function ‘ModbusParseRequest’:
app-layer-modbus.c:1040:13: warning: ‘count’ may be used uninitialized in this function [-Wmaybe-uninitialized]
             ModbusCheckHeaderLength(modbus, tx->length, 2 + count);
             ^
app-layer-modbus.c:964:17: note: ‘count’ was declared here
     uint8_t     count;
                 ^
Actions #1

Updated by Victor Julien over 8 years ago

  • Tracker changed from Optimization to Bug
  • Status changed from Feedback to Assigned
  • Assignee changed from Jason Ish to David DIALLO
  • Target version set to 70

David, can you have a look at this?

Actions #2

Updated by Victor Julien over 8 years ago

  • Description updated (diff)

Cleaned up description.

Actions #3

Updated by Victor Julien over 8 years ago

  • Subject changed from Modbus warnings - when compiling on Fedora 23 to Modbus compiler warnings on Fedora 23
Actions #4

Updated by David DIALLO about 8 years ago

All Modbus warnings generated when compiling 3.0RC3 from source on Fedora 23 are not relevants.

In fact, all variables are initialized thanks to ModbusExtractUint8 or ModbusExtractUint16 function that extracts 8bits or 16bits data from pointer the received input data. In case of extracting error (because of length), ModbusExtractUint8 or ModbusExtractUint16 returns an error that is managed by the caller function.

In any case, all variables can be initialized to zero when they are declared. It does not change anything functionally but it will remove Modbus warnings.

Actions #5

Updated by David DIALLO about 8 years ago

  • Due date set to 02/25/2016
  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100
Actions #6

Updated by Victor Julien about 8 years ago

  • Status changed from Resolved to Closed
  • Target version changed from 70 to 3.0.1RC1
Actions

Also available in: Atom PDF