Hi Hinko,
On 2012-05-21 Hinko Kocevar wrote:
> The problem appears if the user tries to execute dbReportDeviceConfig
> from ioc shell - IOC segFaults.
>
> I've tracked the problem down and it seems that dbReportDeviceConfig()
> is reserving too small buffer to hold @param (40 chars), while
> dbGetString() can return up to 100 chars in the message.
Thanks for the report and patch, which I will add to the Known Problems page.
Your value of 100 actually represents the value of the local macro
messagesize, which I will use instead in case someone changes it in the
future.
- Andrew
--
Never interrupt your enemy when he is making a mistake.
-- Napoleon Bonaparte
- References:
- dbReportDeviceConfig bug Hinko Kocevar
- Navigate by Date:
- Prev:
asynR4-19 available Mark Rivers
- Next:
New sequencer snapshot / release candidate Benjamin Franksen
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
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:
dbReportDeviceConfig bug Hinko Kocevar
- Next:
VMware : won't allow cagets Mogamad Amien Crombie
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
<2012>
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|