ID |
Date |
Author |
Topic |
Subject |
Text |
 |
1298
|
06 Jun 2017 |
Konstantin Olchanski | Bug Report | problem with odb strings and db_get_record() | > Done to all in-tree programs, except for
mana.c (not using it), sequencer.cxx (cannot
test it) and a few places where watching |
|
1216
|
24 Oct 2016 |
Tim Gorringe | Bug Report | problem with error code DB_NO_MEMORY from db_open_record() call when establish additional hotlinks | Hi Midas forum,
I'm having a problem with odb hotlinks after |
|
1218
|
25 Oct 2016 |
Tim Gorringe | Bug Report | problem with error code DB_NO_MEMORY from db_open_record() call when establish additional hotlinks | oOne additional comment. I was able to trace
the setting of the error code DB_NO_MEMORY
|
|
Draft
|
04 Nov 2016 |
Thomas Lindner | Bug Report | problem with error code DB_NO_MEMORY from db_open_record() call when establish additional hotlinks | Hi Tim,
I reproduced your problem and then managed |
|
1220
|
04 Nov 2016 |
Thomas Lindner | Bug Report | problem with error code DB_NO_MEMORY from db_open_record() call when establish additional hotlinks | Hi Tim,
I reproduced your problem and then managed |
|
1221
|
25 Nov 2016 |
Thomas Lindner | Bug Report | problem with error code DB_NO_MEMORY from db_open_record() call when establish additional hotlinks | The procedure I wrote seemed to work for Tim
too, so I added a page to the wiki about
it here:
|
|
434
|
18 Feb 2008 |
Konstantin Olchanski | Bug Report | potential memory corruption in odb,c:extract_key() | It looks like ODB function extract_key() will
overwrite the array pointed to by "key_name"
if given an odb
|
|
444
|
21 Feb 2008 |
Konstantin Olchanski | Bug Report | potential memory corruption in odb,c:extract_key() | > It looks like ODB function extract_key()
will overwrite the array pointed to by "key_name"
if given an odb
|
|
2071
|
13 Jan 2021 |
Isaac Labrie Boulay | Forum | poll_event() is very slow. | Hi all,
I'm currently trying to see if I can speed |
|
2072
|
13 Jan 2021 |
Konstantin Olchanski | Forum | poll_event() is very slow. | >
> I'm currently trying to see if I can speed
up polling in a frontend I'm testing.
|
|
Draft
|
13 Jan 2021 |
Pierre-Andre Amaudruz | Forum | poll_event() is very slow. | > Hi all,
>
> I'm currently trying to see if I can speed |
|
2074
|
13 Jan 2021 |
Stefan Ritt | Forum | poll_event() is very slow. | Something must be wrong on your side. If you
take the example frontend under
|
|
2075
|
14 Jan 2021 |
Pintaudi Giorgio | Forum | poll_event() is very slow. | > Something must be wrong on your side. If
you take the example frontend under
>
|
|
2076
|
14 Jan 2021 |
Isaac Labrie Boulay | Forum | poll_event() is very slow. | > Something must be wrong on your side. If
you take the example frontend under
>
|
|
2077
|
15 Jan 2021 |
Isaac Labrie Boulay | Forum | poll_event() is very slow. | > >
> > I'm currently trying to see if I can
speed up polling in a frontend I'm testing. |
|
2084
|
08 Feb 2021 |
Konstantin Olchanski | Forum | poll_event() is very slow. | > I should mention that I was using midas/examples/Triumf/c++/fevme.cxx
this is correct, the fevme frontend is written |
|
206
|
05 Apr 2005 |
Donald Arseneau | Bug Report | pointers and segfault in yb_any_file_rclose | I'm getting segfaults in yb_any_file_rclose
(closing a file opened with
yb_any_file_ropen with type MIDAS).
|
|
207
|
21 Apr 2005 |
Konstantin Olchanski | Bug Report | pointers and segfault in yb_any_file_rclose | > I'm getting segfaults in yb_any_file_rclose
(closing a file opened with
> yb_any_file_ropen with type MIDAS).
|
|
2966
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | please fix mscb compiler warning | I am getting a scary compiler warning from
MSCB code. I generally avoid touching MSCB
code because I have no MSCB hardware to test |
|
2989
|
21 Mar 2025 |
Stefan Ritt | Bug Report | please fix mscb compiler warning | I hopefully fixed the waring (narrowing down
from size_t to int). Please double check
with your compiler.
|
|