#208968 - 2014-05-30 01:31 AM
Information lacking in error messages
|
It_took_my_meds
Hey THIS is FUN
Registered: 2003-05-07
Posts: 273
Loc: Sydney, Australia
|
Hi Ruud et. al.,
I'm posting this here because I think this is an issue not merely a suggestion. Anyway, this has probably been raised before but there are a number of errors that don't give line numbers or script names. This makes it impossible to track down what script had an issue or even if you know what script it, where the error actually is.
Some examples are:
- Fatal exception occurred.
- KXGetInfo95 Error : The specified module could not be found.
- RasEnumConnections failed
I see this as a significant problem. Can we please have this information for all errors?
Regards,
Richard
|
|
Top
|
|
|
|
|
#208971 - 2014-05-30 04:07 AM
Re: Information lacking in error messages
[Re: It_took_my_meds]
|
Lonkero
KiX Master Guru
Registered: 2001-06-05
Posts: 22346
Loc: OK
|
in principle, fatal exception can't happen. it's like a blue screen. but instead of the whole OS going down, it's just the software. when you get to exception like that, there is no, "hey, lets go backwards in time and look at what happened"
as to what is causing it. bad ram. bad exe-file (corrupt transfer, bad filesystem, bad av)
kixtart, as far as I know, has no managed code in it. it is pure c++ stuff. when things go bad, they really go bad.
if you indeed have fatal exception occurring, the cause needs to be investigated. and my take on it, the environment is 100% the cause. has nothing to do with a script.
if you have lot of these issues, start logging. I always log my scripts. causes more trashy files, but at least I know what was going on week ago tuesday when every one started experiencing drive map issues. or so.
_________________________
!download KiXnet
|
|
Top
|
|
|
|
Moderator: ShaneEP, Arend_, Jochen, Radimus, Glenn Barnas, Allen, Ruud van Velsen, Mart
|
0 registered
and 360 anonymous users online.
|
|
|
