> > since the new server isn't standing here in my office i can not test if older elog
> > versions don't have the problem too. but if your idea of stack or buffer overflow
> > is right, i guess that hoping of the helpfull ms pach or a update of the compiler
> > will be the only what we could do :-( it's always the same using software fom a
> > company named "kleinstweich"... ;-(
>
> ;-))) like that one...
>
> I tried to reduce the memory consumption in the threaded display, can you please try
> the modified version under
>
> http://midas.psi.ch/elog/download/windows/elogd.exe
just was back from work today! i have installed the new elogd.exe file (after a
backup! :-) ) and restarted the service. there are basicalle two news, a really good
one an a bad one:
1. the bad: clicking for a threaded display of the logs will still produce an porobem
as shown in the screendump of the win 2k3 remote controle console (jpeg-attachement).
2. the really good one: the BIG difference to the original 2.5.1 elogd.exe are two
points:
2a) the elgog.exe no more hangs! after a while it comes back to the view before
clicking threaded view. while trying to dispaly the thread it seems to hang, but just
semms! (white browser, nothing to see)
2b) after quitting the error it's bossible to use eleg as normal. no restart of the
service is more needed. before, a restart of the service has to be done because elogd
was hanging compleatly.
as you tought, it looks like a stack problem ore someting else. sorry, didn't had
time enough to find out detailed information of 2k3. also develeoper network from ms
dosn't bring detailed information about memory handling to the public guys like me.
the other solution my be, as i wrote, to have a switch for switching of threaded
display, even a treaded view may be very helpfull in an discussion forum. maybe the
compiler may coming up with a new version or ms will make a pach, for someting
absolutly different of course ;-) , solving this probleme...
ueli
|