Error report (errsysw_.prg)
Re: Error report (errsysw_.prg)
Antonio,
I have no problem with the error, I made it intentionally to check if it works in version 15.07 as it does in version 12.08.
Regards,
Milos
I have no problem with the error, I made it intentionally to check if it works in version 15.07 as it does in version 12.08.
Regards,
Milos
- Antonio Linares
- Site Admin
- Posts: 37481
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Contact:
Re: Error report (errsysw_.prg)
So then, what is the error that you have ?
Re: Error report (errsysw_.prg)
if the user gets an error while using the application in version 12.08 he was able to send me a mail with error.log. I want to go to version 15.07. but this option does not work, why?
I'm sorry for my English
Regards,
Milos
I'm sorry for my English
Regards,
Milos
- Antonio Linares
- Site Admin
- Posts: 37481
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Contact:
Re: Error report (errsysw_.prg)
Milos,
Please post here your errorsys PRG so we can check why sending an email is no longer working, thanks
Please post here your errorsys PRG so we can check why sending an email is no longer working, thanks
Re: Error report (errsysw_.prg)
Several days ago I posted a question on this thread and it disappeared. So I will ask it again.
The suggestion is to NOT use errorsysw.prg. Why ? I took it and modified it to provide very useful information when an error does occur. That is what I link into my application. Using the default would limit the data I can get and that would not be helpful. So, why are you recommending NOT using errorsysw ?
The suggestion is to NOT use errorsysw.prg. Why ? I took it and modified it to provide very useful information when an error does occur. That is what I link into my application. Using the default would limit the data I can get and that would not be helpful. So, why are you recommending NOT using errorsysw ?
Tim Stone
http://www.MasterLinkSoftware.com
timstone@masterlinksoftware.com
Using: FWH 19.06 with Harbour 3.2.0 / Microsoft Visual Studio Community 2019
http://www.MasterLinkSoftware.com
timstone@masterlinksoftware.com
Using: FWH 19.06 with Harbour 3.2.0 / Microsoft Visual Studio Community 2019
Re: Error report (errsysw_.prg)
I'm sorry if I'm not clear (maybe it's because of my bad English ...). In version 15.07, I do not receive an error report (error.log does not exist), while in version 12.08 it exists and could be sent by mail, which is very important to me by the user.
Regards.
Milos
Regards.
Milos
Re: Error report (errsysw_.prg)
It's hard to understand what you want. Do you compile with both versions? Why not compile only with the version that theoretically you say works and generates ERROR.LOG? You do not show anything practical to test or analyze. So it is not possible to help you. Greetings.
João Santos - São Paulo - Brasil
Re: Error report (errsysw_.prg)
I guess what Milos is trying to say is, with ver 15.07 the error occured but no error.log was generated.
With FWH12.08 the error.log was generated.
I'm also interested in this because with latest FWH19.03/05, it's the standard errsysw.prg that is executed not my customized errsysw that I linked in. But then again I may have to check whether I was using hbmk2 or a BCC link script as I just realized with hbmk2 I can't control the order of the objs that gets linked in
With FWH12.08 the error.log was generated.
I'm also interested in this because with latest FWH19.03/05, it's the standard errsysw.prg that is executed not my customized errsysw that I linked in. But then again I may have to check whether I was using hbmk2 or a BCC link script as I just realized with hbmk2 I can't control the order of the objs that gets linked in
FWH 11.08/FWH 19.03
xHarbour 1.2.1 (Rev 6406) + BCC
Harbour 3.1 (Rev 17062) + BCC
Harbour 3.2.0dev (r1904111533) + BCC
xHarbour 1.2.1 (Rev 6406) + BCC
Harbour 3.1 (Rev 17062) + BCC
Harbour 3.2.0dev (r1904111533) + BCC
- nageswaragunupudi
- Posts: 8017
- Joined: Sun Nov 19, 2006 5:22 am
- Location: India
- Contact:
Re: Error report (errsysw_.prg)
You are at liberty to modify and use your own modified program.TimStone wrote:Several days ago I posted a question on this thread and it disappeared. So I will ask it again.
The suggestion is to NOT use errorsysw.prg. Why ? I took it and modified it to provide very useful information when an error does occur. That is what I link into my application. Using the default would limit the data I can get and that would not be helpful. So, why are you recommending NOT using errorsysw ?
The only limitation is that FWH will not be able to support any questions on your modified program.
It is also possible to customize the present FWH's native errsysw.prg. Please review these options and then decide if these options are adequate for your requirements or you really need to replace it with a customized program.
In any case, the original question is different. We will try to address that.
Regards
G. N. Rao.
Hyderabad, India
G. N. Rao.
Hyderabad, India
- nageswaragunupudi
- Posts: 8017
- Joined: Sun Nov 19, 2006 5:22 am
- Location: India
- Contact:
Re: Error report (errsysw_.prg)
Yes, this is the issue raised.hua wrote:I guess what Milos is trying to say is, with ver 15.07 the error occured but no error.log was generated.
With FWH12.08 the error.log was generated.
Wish to have a small test program generating this error and then we can check with both FWH1208 and current version and provide a helpful answer.
Regards
G. N. Rao.
Hyderabad, India
G. N. Rao.
Hyderabad, India
Re: Error report (errsysw_.prg)
Yes, I realize the original question was different, but I was curious about the "why" of one of your responses.
I do realize that if I modify any source code, it is my responsibility to figure out what is going on if I have a problem. Actually, I'm simply reporting more data that I found would be very helpful in understanding the cause of an error when they ( infrequently ) do occur. In fact, I find most errors today are usually due to some change in WIndows rather than a code error.
I usually work off a very recent copy of errorsysw.prg and then add in the extra data lines I need. Thus, my work adds to what already exists and otherwise modifies nothing.
Thank you.
I do realize that if I modify any source code, it is my responsibility to figure out what is going on if I have a problem. Actually, I'm simply reporting more data that I found would be very helpful in understanding the cause of an error when they ( infrequently ) do occur. In fact, I find most errors today are usually due to some change in WIndows rather than a code error.
I usually work off a very recent copy of errorsysw.prg and then add in the extra data lines I need. Thus, my work adds to what already exists and otherwise modifies nothing.
Thank you.
Tim Stone
http://www.MasterLinkSoftware.com
timstone@masterlinksoftware.com
Using: FWH 19.06 with Harbour 3.2.0 / Microsoft Visual Studio Community 2019
http://www.MasterLinkSoftware.com
timstone@masterlinksoftware.com
Using: FWH 19.06 with Harbour 3.2.0 / Microsoft Visual Studio Community 2019
Re: Error report (errsysw_.prg)
Prg:
Exe file:
http://www.smartprint.co.rs/test1208.zip
http://www.smartprint.co.rs/test1507.zip
Regards,
Milos
Code: Select all
#include "FiveWin.ch"
function Main()
* Variable does not exist: MERROR
msgInfo(mError)
return nil
http://www.smartprint.co.rs/test1208.zip
http://www.smartprint.co.rs/test1507.zip
Regards,
Milos
- nageswaragunupudi
- Posts: 8017
- Joined: Sun Nov 19, 2006 5:22 am
- Location: India
- Contact:
Re: Error report (errsysw_.prg)
I copied this program to \fwh1507\samples folder as er.prg and built with "buildx.bat"
This is the error.log I got with native errsysfw.prg:
Please try the same steps I mentioned above.
Code: Select all
buildx er
Code: Select all
Application
===========
Path and name: C:\fwh1507\samples\er.exe (32 bits)
Size: 3,087,872 bytes
Compiler version: xHarbour 1.2.3 Intl. (SimpLex) (Build 20190613)
FiveWin Version: FWHX 15.07
Windows version: 6.2, Build 9200
Time from start: 0 hours 0 mins 0 secs
Error occurred at: 07/06/19, 01:56:38
Error description: Error BASE/1003 Variable does not exist: MERROR
Stack Calls
===========
Called from: er.prg => MAIN( 8 )
Regards
G. N. Rao.
Hyderabad, India
G. N. Rao.
Hyderabad, India
Re: Error report (errsysw_.prg)
Milos, what version of BCC and xHARBOUR are you using to compile with FWH1705?
Regards.
Regards.
João Santos - São Paulo - Brasil