File Pro And Bus Errors

[J. Ryan Kelley]

Jim Asman wrote:

>--------------- Original Message ---------------
>At 11:44A Fri Jul 08 2005, J. Ryan Kelley wrote:
>  
>
>>One of the suggestions that was given to me to track down the source of 
>>these bus errors was to run the code through dclerk w/ the -db argument 
>>to debug to see exactly where these bus errors are occuring, oddly 
>>enough most (if not all) of these bus errors are occuring before debug 
>>even begins to go through any of the code, yet if I run debug with out 
>>input processing (-z xxyyzzz) all goes well.  Any ideas?
>>    
>>
>
>What happens if you tokenize the processing and then run from
>rclerk/rreport?
>
>
>Jim 
>--
>jlasman at telus.net                       Spectra Colour Services Ltd.
>Jim Asman                               10221 144A Street
>Phone: (604)584-0977                    Surrey, BC  V3R 3P7             
> Cell: (604)619-0977                    CANADA
>
>_______________________________________________
>Filepro-list mailing list
>Filepro-list at lists.celestial.com
>http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>
>  
>
In this case at least running rclerk gives no problems at all, so the 
obvious solution is to run it always through rclerk, which we do for the 
general employees here.  However we occasionally will have a locked 
index, and the easieast way (at least that I know of) to find out what 
index is holding everything up is to run through the code in debug until 
it hangs, then rebuild the index of the look up that the code is hanging 
on, not to mention dclerk is still a great resource for testing new code.

-- 
J. Ryan Kelley
Trinity Transport, Inc.
(302)253-3900 ext. 3844