> > I have a problem here which the ELOG service get terminated unexpectedly
> > on the Windows Server.
> > Is there any way to debug this problem ?
> 
> One can start the elogd server manually. So stop the service, and start 
> 
> c:\program files\elogd\elogd.exe -v
> 
> The "-v" flag shows all network traffic between the server and the browser. So
> maybe the last conversation before the crash can tell us something. Make a
> screendump of it and send it to me.

Here is the screen dump after we perform a deletion .
Another my the other thread , i show another dump when a move is perform

regards

GET /IFSOCC+Current/1?cmd=Delete&nextmsg=0&confirm=Yes HTTP/1.0
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-
powerpoint, application/vnd.ms-excel, application/msword, application/x-shockwav
e-flash, */*
Referer: http://sinccbap2kp38.sq.com.sg:8877/IFSOCC+Current/1?cmd=Delete
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
Host: sinccbap2kp38.sq.com.sg:8877
Connection: Keep-Alive
Cookie: urem=0; unm=ifsocc; upwd=dHBmc3Bk; SMSESSION=uvdhD3MUFAkDID0huNAnYhdoJxb
R74QgLwDYms+cAciPxtHlh0AIjpAqlgu6zcCeRzGLP3h7N/quulR8Z3KTWG0GQ7TQ9hdggdHTre8aoUW
YbAdTKbkWCJS/mDrfZbspmu/SiA0l4z1UEF7VAq79h78/ErlnUZPmQdbSacqYhD2Np3zqfy1GyMUtqGu
W2IW+iy5M4e7d6cIt9wkr5VmezTkmfzf8lE3RiYhE/bkjL7xBkDefFY/6tBcS28zoqBW1LhqZVnkq9FS
l5MS0vKiTDmiWusHkaD9iRaq1Gmk0lhzzvoQQ8n9ZD3ICzWAqEifRvMoqEWs1AkRA7ghEI6ONg27ffI+
F32gqXZqY7Je3I7tZOl2e4br2biwqRaQo8Rc2wztY4XxOaxdQVcbbzy1pcz9yRU6c+UTPaTNVj91o/mD
Cv+lojTVB6i6AVEqa7rgSObxGmcvYsmEIzFUqVwhgTkAYlCLMLp7Fy1HzWVj5u14bYhq53kGJaqa+SKE
FejtwlUWj7cgTkNLubCAStWUyAYwNeqDyVaYFz6HapDiXrpRNtn0cydS2zcJ1kfynloBWBp1f1vbW3U6
bCZEp6GQOUXSyWuGyP/k/umB9JrfBkstCoiou3pIWNG1Sf7Ni0+vLyaZFIt5YEDdkb3TXIZlIUjAFOsk
t3KVnfdtomNoE6cvsFIG9kJxCr6b7TIJAS+RxGQUYmHCK6R1oIUx9ZL8qXnjvDY2dGjyZg5aCYUx8smh
3DOO7WykAqEiPcNt7I1K4kwX1E+Eu5d/Y5X+qEZ553H4wNnlA/nXod374ksQ2AFqK9HVomVIi9AJg9sO
6ygrsRDArVPMjnzKatCb8yNTnor4dphH18XoANpvbvkmIUSRh+gwHNznLGE1blbfiOrxhXNVBVmfl1iU
Yts2NTkEQu4xwnooDA7YZ


xrealloc: not enough memory

1.

I do not know if this is a problen of the 2.5.5 (11/03/04) version or of
other versions as well:

I'm using the $message id parameter in a substitution:
Subst KlientIn/KundIn = $Vorname $Name; P: $Telefon Privat; G: $Telefon
Geschäft; N: $Telefon Mobil; $Landeskennung-$PLZ $Ortschaft [<a
href="http://localhost:8080/$logbook/$message id">$logbook:$mesage id</a>]

the "$message id" will not be replaced by the msg id, the string "$message
id"  will be dispalyed and used. Other substitutions as $logbook etc. are
working.

Is this a bug or did i missunderstood the manual?


2.

Since Version 2.5.5: If ELOG is running under German, the "Zurück" Bottom is
named "Back". Any Idee where I can change this back?  ;-)

2.5.4-6 was corretly translated.

> the "$message id" will not be replaced by the msg id, the string "$message
> id"  will be dispalyed and used. Other substitutions as $logbook etc. are
> working.
> 
> Is this a bug or did i missunderstood the manual?

Well, the manual does not state that "$message id" should work for "Subst
<attribute>" option (;-)

The reason is that the message ID is available only *after* a new entry has been
written to the database, and the "Subst" command is evaluated *before* an entry
is submitted. "$message id" only works for "Thread display", "RSS Title", "Subst
on reply", "Subst on edit" and "Display". You should use

Display KlientIn/KundIn = $Vorname $Name; P: $Telefon Privat; G: $Telefon
Geschaft; N: $Telefon Mobil; $Landeskennung-$PLZ $Ortschaft [<a
href="http://localhost:8080/$logbook/$message id">$logbook:$message id</a>]

Please note that you wrote "mesage id", correct is however "message id" (two
"s"), so there is also a typo.

> Since Version 2.5.5: If ELOG is running under German, the "Zurück" Bottom is
> named "Back". Any Idee where I can change this back?  ;-)

The link "Back" has been replaced upon request by "List" which is more
appropriate. So if you changed your menu with "Menu commands = ...", please
replace "Back" by "List" there.

1. thats now clear with the £message id and the work-around is ok for my 
needs

2. the "bacl" link is clear and tranlated to "Liste". But I mean the back 
button 
in the entry and the edit mode (see picture)...  ;-)

> > the "$message id" will not be replaced by the msg id, the 
string "$message
> > id"  will be dispalyed and used. Other substitutions as $logbook etc. 
are
> > working.
> > 
> > Is this a bug or did i missunderstood the manual?
> 
> Well, the manual does not state that "$message id" should work for "Subst
> <attribute>" option (;-)
> 
> The reason is that the message ID is available only *after* a new entry 
has been
> written to the database, and the "Subst" command is evaluated *before* 
an entry
> is submitted. "$message id" only works for "Thread display", "RSS 
Title", "Subst
> on reply", "Subst on edit" and "Display". You should use
> 
> Display KlientIn/KundIn = $Vorname $Name; P: $Telefon Privat; G: $Telefon
> Geschaft; N: $Telefon Mobil; $Landeskennung-$PLZ $Ortschaft [<a
> href="http://localhost:8080/$logbook/$message id">$logbook:$message 
id</a>]
> 
> Please note that you wrote "mesage id", correct is however "message id" 
(two
> "s"), so there is also a typo.
> 
> > Since Version 2.5.5: If ELOG is running under German, the "Zurück" 
Bottom is
> > named "Back". Any Idee where I can change this back?  ;-)
> 
> The link "Back" has been replaced upon request by "List" which is more
> appropriate. So if you changed your menu with "Menu commands = ...", 
please
> replace "Back" by "List" there.

> 2. the "bacl" link is clear and tranlated to "Liste". But I mean the back 
> button 
> in the entry and the edit mode (see picture)...  ;-)

Well, if you try with the demo logbook, the "Back" button is translated
correctly, so I don't know whats wong in your case. Can you check that your
eloglang.german file is intact?

installed elog 2.5.5 agin, same effekt with "back" / "zurück". checked the 
language file eloglang.german witch seem ok for me and the translations are 
well done. removed then in eloglang.germen the traslation for back and checked 
this: still back was viewed. reinserted the translation "Zurück" (just this 
word!)and checked again: everithing looks fine, no longer back, correctly 
Zurück on the button.
absolutly no idea why and whats the difference was! bus it works...
thank's stefan!  :-)

> > 2. the "back" link is clear and tranlated to "Liste". But I mean the back 
> > button 
> > in the entry and the edit mode (see picture)...  ;-)
> 
> Well, if you try with the demo logbook, the "Back" button is translated
> correctly, so I don't know whats wong in your case. Can you check that your
> eloglang.german file is intact?

When compiling elogd on AMD64 (in 64 bit mode) there are many 
warnings like these:

src/regex.c:3769: warning: cast from pointer to integer of different size
src/regex.c:3769: warning: cast from pointer to integer of different size
src/regex.c:3775: warning: cast to pointer from integer of different size

The reason is the (int) cast, which (I think) is not necessary.

> When compiling elogd on AMD64 (in 64 bit mode) there are many 
> warnings like these:
> 
> src/regex.c:3769: warning: cast from pointer to integer of different size
> src/regex.c:3769: warning: cast from pointer to integer of different size
> src/regex.c:3775: warning: cast to pointer from integer of different size
> 
> The reason is the (int) cast, which (I think) is not necessary.

Unfortunately I don't have a 64-bit compiler to try. Can you please check if
elogd.c has similar warnings or only regex.c? The ones in elogd.c I can fix,
but regex.c is straight from the GNU C library, so we would have to wait intil
they fix it. Or can you get it from the 64-bit C library? The point is that I
need the source code, so that I can compile it under Windows as well. Can you
try to compile elogd without regex.c, like 

gcc -g -O -W -Wall -o elogd src/elogd.c

If that works fine, we don't have to compile regex.c under linux. But I guess
it's still needed fot Solaris and other non-GNU Unix brands.