|
|
|
Back
Midas
Rome
Roody
Rootana
|
| Midas DAQ System |
Not logged in |
 |
|
23 Apr 2026, Pavel Murat, Bug Report, increasing the max number of hot links in ODB
|
24 Apr 2026, Konstantin Olchanski, Bug Report, increasing the max number of hot links in ODB
|
25 Apr 2026, Pavel Murat, Bug Report, increasing the max number of hot links in ODB
|
27 Apr 2026, Konstantin Olchanski, Bug Report, increasing the max number of hot links in ODB
|
27 Apr 2026, Pavel Murat, Bug Report, increasing the max number of hot links in ODB
|
26 Apr 2026, Stefan Ritt, Bug Report, increasing the max number of hot links in ODB
|
27 Apr 2026, Konstantin Olchanski, Bug Report, increasing the max number of hot links in ODB
|
27 Apr 2026, Nick Hastings, Bug Report, increasing the max number of hot links in ODB
|
27 Apr 2026, Pavel Murat, Bug Report, increasing the max number of hot links in ODB
|
27 Apr 2026, Pavel Murat, Bug Report, increasing the max number of hot links in ODB
|
|
|
Message ID: 3210
Entry time: 23 Apr 2026
Reply to this: 3211
3212
3214
|
| Author: |
Pavel Murat |
| Topic: |
Bug Report |
| Subject: |
increasing the max number of hot links in ODB |
|
|
Dear MIDAS experts,
when I attempted to increase the max number of hotlinks in ODB , defined as
#define MAX_OPEN_RECORDS 256 /**< number of open DB records */
I started running into an assertion in midas/src/odb.cxx
https://bitbucket.org/tmidas/midas/src/fa5457b5274a6b42c5ed8b6dea5e3cdd43de38fe/src/odb.cxx#lines-1525 :
assert(sizeof(DATABASE_CLIENT) == 2112);
is it possible that the size of the DATABASE_CLIENT structure should be checked against 64+sizeof(OPEN_RECORD)*MAX_OPEN_RECORDS ?
- 64 clearly can be expressed in a better maintainable form
UPDATE: similar consideration holds for the size of the DATABLE_HEADER structure, which is also checked against a constant
https://bitbucket.org/tmidas/midas/src/fa5457b5274a6b42c5ed8b6dea5e3cdd43de38fe/src/odb.cxx#lines-1526
-- many thanks, regards, Pavel
|