[UV] Fault type 4

2004-03-29 Thread Mike Farrant
We have a problem with a piece of code that we have been debugging all
day so far with no progress.

A transaction process runs through the same bit of code several times
without a problem, then for no 'apparent' reason (I guess there is one
there some-where) the programme kicks up with:

 

Abnormal Termination of UniVerse.

Fault type is 4.  Layer type is BASIC run machine

Fault occurred in BASIC program  at address 5004.

 

Can anyone tell me what this fault means - if anything?

 

We have re-compiled the code, checked all the data files for corruptions
and thrown it into debug - unfortunately because we cannot re-create the
problem consistently, it may take hours still to find the exact place
where it crashes.

 

Any help would be appreciated...

 

Thanks in advance,

 

Mike

--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users


Re: [UV] Fault type 4

2004-03-29 Thread David T. Meeks
Basically, it means that you've hit a SIGILL, an illegal instruction signal,
during the execution of the BASIC program, at address 5004.
If that part of the error message is consistent (the address 5004), you can
determine WHERE in the program it is failing by looking at the VLIST listing.
I'd suggest contacting IBM support, as this represents some internal
failure that you need to have assessed and corrected.  It may be a known
issue that already has a fix.
Dave

At 07:36 AM 3/29/2004 -0500, you wrote:
We have a problem with a piece of code that we have been debugging all
day so far with no progress.
A transaction process runs through the same bit of code several times
without a problem, then for no 'apparent' reason (I guess there is one
there some-where) the programme kicks up with:


Abnormal Termination of UniVerse.

Fault type is 4.  Layer type is BASIC run machine

Fault occurred in BASIC program  at address 5004.



Can anyone tell me what this fault means - if anything?



We have re-compiled the code, checked all the data files for corruptions
and thrown it into debug - unfortunately because we cannot re-create the
problem consistently, it may take hours still to find the exact place
where it crashes.


Any help would be appreciated...



Thanks in advance,



Mike

--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users

David T. Meeks || "All my life I'm taken by surprise
Architect, Technology Office   || I'm someone's waste of time
Ascential Software ||  Now I walk a balanced line
[EMAIL PROTECTED]   ||  and step into tomorrow" - IQ

--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users