Incomprehensible error messages

This is a discussion on Incomprehensible error messages within the Clipper forums in Programming Languages category; Quite some times, the errorlog yields an error+description which doesn't make sense at all. For example: Error Code: 1 [ ] Subsystem: BASE Operation: NULL_ARRAY Function: ARRAYGET Argument: 107 Argument Number: 1 CallStack: and this is the line: IF odbjPost:SEEK(cDagboek+cJaar+cBoekstuk) .OR. lAppend It happens now and then and I see no reason why anything is wrong with the database or the 3 character and 1 logic protected variables...or the if statement... So I wonder seeing an error like this: What has this line to do with arrayget? There's no array involved at all. What is "argument: 107" What can be ...

Go Back   Application Development Forum > Programming Languages > Clipper

Object Mix

Register FAQ Calendar Search Today's Posts Mark Forums Read
  #1  
Old 08-20-2008, 05:38 PM
D.J.W. van Kooten
Guest
 
Default Incomprehensible error messages

Quite some times, the errorlog yields an error+description which
doesn't make sense at all. For example:

Error Code: 1 [ ]
Subsystem: BASE
Operation: NULL_ARRAY
Function: ARRAYGET
Argument: 107
Argument Number: 1
CallStack:

and this is the line:

IF odbjPost:SEEK(cDagboek+cJaar+cBoekstuk) .OR. lAppend

It happens now and then and I see no reason why anything is wrong with
the database or the 3 character and 1 logic protected variables...or
the if statement...

So I wonder seeing an error like this:

What has this line to do with arrayget? There's no array involved at
all.
What is "argument: 107"
What can be wrong here?

Any comments are welcome...

Dick van Kooten
Reply With Quote
  #2  
Old 08-20-2008, 07:14 PM
Stephen Quinn
Guest
 
Default Re: Incomprehensible error messages

Dick

My guess

> Error Code: 1 [ ]
> Subsystem: BASE
> Operation: NULL_ARRAY
> Function: ARRAYGET
> Argument: 107
> Argument Number: 1

Wrong parameter type passed to ArrayGet()
Eg
xResult := ArrayGet( 107 )
possibly should be
xResult := ArrayGet( anArray, 107 )

It's probably happening the the Seek() method, you might peruse the SDK
and/or the RDD API source to see if it uses arrays internally.

Maybe caused by a bit of corrupt memory or the GC kicking in or the user
holding the mouse in an inappropriate way.

As I said - a guess.

CYA
Steve


Reply With Quote
  #3  
Old 08-21-2008, 06:40 AM
D.J.W. van Kooten
Guest
 
Default Re: Incomprehensible error messages

On Wed, 20 Aug 2008 23:14:47 GMT, "Stephen Quinn"
<stevejqNO@SPbigpond.AMnet.au> wrote:

Hello Steve,

>Wrong parameter type passed to ArrayGet()
>Eg
> xResult := ArrayGet( 107 )
>possibly should be
> xResult := ArrayGet( anArray, 107 )


>It's probably happening the the Seek() method, you might peruse the SDK
>and/or the RDD API source to see if it uses arrays internally.


Still I don't understand how arrayget can be involved. I've checked if
it could be possible that the first paramater is assigned an array
instead of a string. In all cases, the ocombobox:value is assigned and
this is a string. But even - suppose I would send an array, where is
the arraget function coming from then in the errorlog when I use a
seek? I don't use it anywwhere in my application and it isn't used in
the whole RDD SDK.

I've seen this quite to often and think that the errorlog stuffs half
of it's output with random functions...

Dick
Reply With Quote
  #4  
Old 08-21-2008, 11:54 AM
Amilcar A. Camargo
Guest
 
Default Re: Incomprehensible error messages

Hi Dick,

On Wed, 20 Aug 2008 23:38:48 +0200, D.J.W. van Kooten
<public@ic2remove.this.com> wrote:

>Quite some times, the errorlog yields an error+description which
>doesn't make sense at all. For example:
>
>Error Code: 1 [ ]
>Subsystem: BASE
>Operation: NULL_ARRAY
>Function: ARRAYGET
>Argument: 107
>Argument Number: 1
>CallStack:


This error used to happen frequently in 2.6 and was caused by repo. Try a repo
reindex and touch. I see it when getting a ClassList() and ocurred internally
in CAVO functions. Give it a try.

HTH,
Amilcar A. Camargo F.
Guatemala, C. A.
Reply With Quote
  #5  
Old 08-21-2008, 07:38 PM
Stephen Quinn
Guest
 
Default Re: Incomprehensible error messages

Dick

> Still I don't understand how arrayget can be involved. I've checked if
> it could be possible that the first paramater is assigned an array


The internals of the RDD may use arrays and that is where the error is
raised - might have nothing to do with *your* code use - memory corruption
(assuming that's what's causing it) can happen anywhere in the app.

> seek? I don't use it anywwhere in my application and it isn't used in
> the whole RDD SDK.


You don't have the whole source to the RDD API (the SDK (VO source) is only
a wrapper around the system RDD DLLs) so how do you know.

Is this ERROR happening on a single machine or lots of machines??
Which OS is used on these machines, memory, etc...

CYA
Steve


Reply With Quote
Reply


Thread Tools
Display Modes


All times are GMT -5. The time now is 10:25 AM.


Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.2.0
vB Ad Management by =RedTyger=

In an effort to better serve ads to our visitors, cookies are used on objectmix.com. For more information, check out our Privacy Policy.