modules/database/src/std/rec/biRecord.c
argument to 'sizeof' in 'strncpy' call is the same
expression as the source; did you mean to use the size
of the destination? [-Wsizeof-pointer-memaccess]
line:char 184:42 187:42 201:43 203:43 331:42 334:42
A sizeof znam/onam field size is used as the size limit
for strncpy; GCC suspects it to be a mistake and warns.
Unfortunately, the size is specified as a number in
biRecord.h - a fix should change the generator to use
a name and #define the name, and then use the name
instead the sizeof (using a number in the biRecord.c
would remove the warning, but the code would become
wrong without a warning if the size was changed later).
--
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1905159
Title:
Fix warnings from recent compiler versions
Status in EPICS Base:
Triaged
Bug description:
Builds of EPICS Base using recent versions of gcc, clang and MSVC
generate compiler warnings, which we try to minimize if possible. Some
of these warnings can be prevented with suitable code modifications,
although the code must still build on the older compilers and other
architectures that we support.
Both the 3.15 and 7.0 branches can be examined for warnings; fixes
made on the 3.15 branch get propagated to the 7.0 branch during
periodic up-merges, so there is no need to make the same changes to
both branches. Some code only exists on one branch; for example the
gdd module was unbundled after 3.15, and there are many new modules in
7.0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1905159/+subscriptions
- Navigate by Date:
- Prev:
[Bug 1905159] Re: Fix warnings from recent compiler versions Jerzy Tarasiuk via Core-talk
- Next:
Build failed in Jenkins: EPICS-3.14 #1067 Jenkins EPICS PSI via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
<2021>
2022
2023
2024
- Navigate by Thread:
- Prev:
[Bug 1905159] Re: Fix warnings from recent compiler versions Jerzy Tarasiuk via Core-talk
- Next:
[Bug 1182091] Re: Make TIME field directly accessible Jure Varlec via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
<2021>
2022
2023
2024
|