On 04/18/2017 10:20 AM, Michael Davidsaver wrote:
> I haven't been able to replicate this apparent crash. Can you get a
> stack trace?
I suspect you meant something like this:
> diff --git a/src/ioc/db/dbUnitTest.c b/src/ioc/db/dbUnitTest.c
> index 7764f78..a92f8de 100644
> --- a/src/ioc/db/dbUnitTest.c
> +++ b/src/ioc/db/dbUnitTest.c
> @@ -196,7 +196,8 @@ void testdbGetArrFieldEqual(const char* pv, short dbfType, long nRequest, unsign
> const long vSize = dbValueSize(dbfType);
> const long nStore = vSize * nRequest;
> long status;
> - char *gbuf, *gstore, *pbuf = pbuf;
> + char *gbuf, *gstore;
> + const char *pbuf = pbufraw;
>
> if(dbNameToAddr(pv, &addr)) {
> testFail("Missing PV \"%s\"", pv);
It surpsises me that gcc didn't warn about self-assignment of an
undefined value.
Please apply both fixes to 3.16 after the Jenkins test jobs have passed.
- Andrew
--
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon
- Replies:
- Re: Jenkins build became unstable: epics-base-3.15 #311 Michael Davidsaver
- References:
- Jenkins build became unstable: epics-base-3.15 #311 APS Jenkins
- Re: Jenkins build became unstable: epics-base-3.15 #311 Andrew Johnson
- Re: Jenkins build became unstable: epics-base-3.15 #311 Michael Davidsaver
- Navigate by Date:
- Prev:
Re: Jenkins build became unstable: epics-base-3.15 #311 Michael Davidsaver
- Next:
Jenkins build is back to stable : epics-base-3.15 #312 APS Jenkins
- 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:
Re: Jenkins build became unstable: epics-base-3.15 #311 Michael Davidsaver
- Next:
Re: Jenkins build became unstable: epics-base-3.15 #311 Michael Davidsaver
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
<2017>
2018
2019
2020
2021
2022
2023
2024
|