| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
661
|
11 Oct 2009 |
Konstantin Olchanski | Bug Report | Multiple definition of `SqlODBC::SqlODBC() | > > Why is the class "SqlODBC" duplicated?
>
> This is interesting. I do not think my |
|
|
676
|
25 Nov 2009 |
Konstantin Olchanski | Bug Report | once in 100 years midas shared memory bug | We were debugging a strange problem in the
event builder, where out of 14
fragments, two fragments were always getting |
|
|
678
|
26 Nov 2009 |
Konstantin Olchanski | Bug Report | "mserver -s" is broken | I notice that "mserver -s" (a non-default
mode of operation) does not work right
- if I connect odbedit for the first time, |
|
|
680
|
27 Nov 2009 |
Stefan Ritt | Bug Report | "mserver -s" is broken | > I notice that "mserver -s" (a non-default
mode of operation) does not work right
> - if I connect odbedit for the first time, |
|
|
681
|
27 Nov 2009 |
Konstantin Olchanski | Bug Report | "mserver -s" is broken | >
> "mserver -s" is there for historical reasons
and for debugging.
|
|
|
728
|
06 Oct 2010 |
Konstantin Olchanski | Bug Report | mhttpd "edit on start" breakage | very recent mhttpd mangles spaces in URL encoding-decoding
and I cannot create or delete entries in
for
|
|
|
732
|
17 Nov 2010 |
Stefan Ritt | Bug Report | mhttpd "edit on start" breakage | > very recent mhttpd mangles spaces in URL
encoding-decoding and I cannot create or
delete entries in for
|
|
|
734
|
23 Dec 2010 |
Konstantin Olchanski | Bug Report | odb corruption, odb race condition? | The following script makes midas very unhappy
and eventually causes odb corruption. I suspect
the reason is some kind of race condition |
|
|
735
|
24 Dec 2010 |
Konstantin Olchanski | Bug Report | odb corruption, odb race condition? | > Thu Dec 23 12:10:30 2010 [ODBEdit9,ERROR]
[odb.c:3247:db_get_value,ERROR] "Name" is
of type NULL, not STRING
|
|
|
736
|
24 Dec 2010 |
Konstantin Olchanski | Bug Report | odb corruption, odb race condition? | > > Thu Dec 23 12:10:30 2010 [ODBEdit9,ERROR]
[odb.c:3247:db_get_value,ERROR] "Name" is
of type NULL, not STRING
|
|
|
737
|
26 Dec 2010 |
Konstantin Olchanski | Bug Report | race condition and deadlock between ODB lock and SYSMSG lock in cm_msg() | >
> The only remaining problem when running
my script is some kind of deadlock between |
|
|
738
|
29 Dec 2010 |
Konstantin Olchanski | Bug Report | use of nested locks in MIDAS | A "nested" or "recursive" lock is a special
type of lock that permits a lock holder to
lock the same resources again and again, |
|
|
739
|
29 Dec 2010 |
Konstantin Olchanski | Bug Report | fixed. odb corruption, odb race condition? | >
> The only remaining problem when running
my script is some kind of deadlock between |
|
|
740
|
17 Jan 2011 |
Andreas Suter | Bug Report | Problems with midas history SVN 4936 | I have the following problems after updating
to midas SVN 4936: the history
system (web-page via mhttpd) seems to stop |
|
|
741
|
11 Feb 2011 |
Konstantin Olchanski | Bug Report | fixed. odb corruption, odb race condition? | > >
> > The only remaining problem when running
my script is some kind of deadlock between |
|
|
742
|
13 Feb 2011 |
Lee Pool | Bug Report | Problems with midas history SVN 4936 | > I have the following problems after updating
to midas SVN 4936: the history
> system (web-page via mhttpd) seems to stop |
|
|
743
|
15 Feb 2011 |
Konstantin Olchanski | Bug Report | fixed. odb corruption, odb race condition? | > Solution shall follow quickly, I have been
hunting this deadlock for the last couple
of weeks...
|
|
|
746
|
16 Feb 2011 |
Konstantin Olchanski | Bug Report | Problems with midas history SVN 4936 | > I have the following problems after updating
to midas SVN 4936: the history
> system (web-page via mhttpd) seems to stop |
|
|
747
|
16 Feb 2011 |
Konstantin Olchanski | Bug Report | Problems with midas history SVN 4936 | It looks like email notices did not go the
first time. Please read my replies below.
K.O.
|
|
|
748
|
16 Feb 2011 |
Konstantin Olchanski | Bug Report | Problems with midas history SVN 4936 | >
> Do you mind giving little more detail?
We might have the same issue, where we got
|
|