| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2848
|
16 Sep 2024 |
Stefan Ritt | Bug Report | Crash using ODB watch | Well, the object *went* out of scope. For
my code it‘s hard to realize this, so the
error reporting is poor. Also the first object |
|
|
2849
|
16 Sep 2024 |
Marius Koeppel | Bug Report | Crash using ODB watch | Okay, but this is then a big issue IMO. For
Mu3e we do this in every frontend and I also
checked again all of these watches are broken |
|
|
2850
|
16 Sep 2024 |
Mark Grimes | Bug Report | Crash using ODB watch | Hi,
Maybe I've misunderstood the code, but odb::watch()
creates a deep copy of itself to set the |
|
|
2851
|
17 Sep 2024 |
Konstantin Olchanski | Bug Report | Crash using ODB watch | > {
> odb new_settings("/Equipment/Test FE/Settings");
> new_settings.watch(watch); // <-- here |
|
|
2852
|
18 Sep 2024 |
Marius Koeppel | Bug Report | Crash using ODB watch | I created a PR to fix this issue https://bitbucket.org/tmidas/midas/pull-requests/42.
The crash happened since the change in commit
3ad98c5 always got the ODB via XML.
|
|
|
2853
|
20 Sep 2024 |
Stefan Ritt | Bug Report | Crash using ODB watch | The problem has been fixed in the current
version. Here is my analysis:
|
|
|
819
|
04 Jul 2012 |
Konstantin Olchanski | Bug Report | Crash after recursive use of rpc_execute() | I am looking at a MIDAS kaboom when running
out of space on the data disk - everything
was freezing
|
|
|
820
|
04 Jul 2012 |
Konstantin Olchanski | Bug Report | Crash after recursive use of rpc_execute() | > ... I see a recursive call to rpc_execute():
rpc_execute() calls tr_stop() calls cm_yield()
calls
|
|
|
821
|
13 Jul 2012 |
Stefan Ritt | Bug Report | Crash after recursive use of rpc_execute() | > Then I realized that I see a recursive call
to rpc_execute(): rpc_execute() calls tr_stop()
calls cm_yield() calls
|
|
|
618
|
18 Aug 2009 |
Denis Calvet | Suggestion | Could not create strings other than 32 characters with odbedit -c "..." command | Hi,
I am writing shell scripts to create some
tree structure in an ODB. When
|
|
|
627
|
03 Sep 2009 |
Stefan Ritt | Suggestion | Could not create strings other than 32 characters with odbedit -c "..." command | > Hi,
> I am writing shell scripts to create some
tree structure in an ODB. When
|
|
|
634
|
06 Sep 2009 |
Exaos Lee | Suggestion | Could not create strings other than 32 characters with odbedit -c "..." command | > Ok, I added a command
>
> odbedit -c "create STRING Test[8][40]"
|
|
|
640
|
06 Sep 2009 |
Exaos Lee | Suggestion | Could not create strings other than 32 characters with odbedit -c "..." command | > > Ok, I added a command
> >
> > odbedit -c "create STRING Test[8][40]"
|
|
|
208
|
21 Apr 2005 |
Konstantin Olchanski | Suggestion | Correct MIDASSYS setting? | Current MIDAS versions nag me about setting
the env.variable MIDASSYS to the
"midas installation directory", but I do |
|
|
209
|
22 Apr 2005 |
Stefan Ritt | Suggestion | Correct MIDASSYS setting? | > Current MIDAS versions nag me about setting
the env.variable MIDASSYS to the
> "midas installation directory", but I do |
|
|
1905
|
07 May 2020 |
Estelle | Bug Report | Conflic between Rootana and midas about the redefinition of TID_xxx data types | Dear Midas and Rootana people,
We have tried to update our midas DAQ with |
|
|
1911
|
20 May 2020 |
Konstantin Olchanski | Bug Report | Conflic between Rootana and midas about the redefinition of TID_xxx data types | > Dear Midas and Rootana people,
>
> We have tried to update our midas DAQ with |
|
|
854
|
24 Jan 2013 |
Konstantin Olchanski | Info | Compression benchmarks | In the DEAP experiment, the normal MIDAS mlogger
gzip compression is not fast enough for
some data
|
|
|
858
|
06 Feb 2013 |
Stefan Ritt | Info | Compression benchmarks | I redid the tests from Konstantin for our
MEG experiment at PSI. The event structure
is different, so it
|
|
|
334
|
02 Feb 2007 |
Exaos Lee | Bug Report | Compiling failed with SVN3562 under Ubuntu 6.10 | The error log is as the following:
[CODE]
cc -c -g -O2 -Wall -Wuninitialized -Iinclude |
|