Hi,
How can change name of this log file from application ? Is this only possible with create or change errorsys.prg ?
I have main application, and this run paralell several exe modules, which run paralell.
When some of them break, every write to same log file.
I want to every app write to own log file because it is problem to analyze errors.
exe files are in same directory as main application and exe files are created also in Xbase++.
Or I want create some error manager, which send me errors from clients application to analyze, but need know, from which user or from which IP adress this come.
thx
XPPFATAL.LOG change name
Re: XPPFATAL.LOG change name
Best regards,
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Re: XPPFATAL.LOG change name
ok, then i must try if can run external modules from other directories but this can be problem because dlls etc...
Re: XPPFATAL.LOG change name
The XPPFATAL.LOG will always be written to the folder of the .EXE.
You could try putting your .EXEs in different folders.
You could try putting your .EXEs in different folders.
The eXpress train is coming - and it has more cars.
Re: XPPFATAL.LOG change name
As long as the EXE is able to write there.The XPPFATAL.LOG will always be written to the folder of the .EXE.
Best regards,
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Re: XPPFATAL.LOG change name
It is true, because it is not safe full rw access do program directory, especially on Lan.
This mean, to no possible change creating xppfatal.log with own errorsys function ? I have some old errorsys.prg from Clipper, but for xbase++ it is not applicable and also there is nothing about creating error file.
I am searching solution for this, because I have problem to analyze errors when running 12 processes paralell on 12 CPU cores, and some from this crash. User do not want wait for my analyze and then break all processes , this rewrite xppfatal and I do not see error which "start" problem.
This mean, to no possible change creating xppfatal.log with own errorsys function ? I have some old errorsys.prg from Clipper, but for xbase++ it is not applicable and also there is nothing about creating error file.
I am searching solution for this, because I have problem to analyze errors when running 12 processes paralell on 12 CPU cores, and some from this crash. User do not want wait for my analyze and then break all processes , this rewrite xppfatal and I do not see error which "start" problem.
Re: XPPFATAL.LOG change name
You can do whatever you want in your own Errorsys. You can track errors, write mails, correct problems, rename files, whatever you need.
XPPFATAL.LOG has nothing to do with the runtime error handling. It's created if the app runs into a fatal ("deadly") error and is not able to call the errorsys.
XPPFATAL.LOG has nothing to do with the runtime error handling. It's created if the app runs into a fatal ("deadly") error and is not able to call the errorsys.
Best regards,
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Re: XPPFATAL.LOG change name
ok, thank you for explanation.