[net.misc] Program bug

neal@gymble.UUCP (Neal R. Vanderlipp) (08/17/85)

>> My program crashed. Can anyone debug it for me? Here's the core dump:
>> 
>> 
>> 0000000  000000 000000 000000 000000 000000 000000 000000 000000
>> 0000020  000000 000000 000000 000000 000000 000000 000000 000000
>> 0000040  000000 000000 000000 000000 000000 000000 000000 000000
>>  .
>>  .
>>  .
>> 0002220  000000 000000 000000 000000 000000 000000 000000 000000
>> 0002240  000000 000000 000000 000000 000000 000000 000000 000000
>> 0002260  000000 000000 000000 000000 000000 000000 000000 000000
>> 0002300  000000 000002 000000 000010 000000 004065 000000 000000
>> 0002320  000000 000000 000000 000000 000000 000000 000000 000000
>> 0002340  000000 000000 000000 000000 000000 000000 000000 000000
>> -- 
>> Neal R. Vanderlipp 

>Of course!  Line 112 is:
>0002220  000000 000000 000000 000000 000000 000000 000000 000000
>when it should be:
>0002220  000000 000010 000000 000000 000000 000020 000000 000000
>BUT!  I can tell by all the zeros in the file that this program
>was written in COBOL!!  Shame, shame...
>-- 

>  Allen Grabert 


Allen, what's COBOL?    
By the way, this was coded in Hieroglyphi-C on a Pyramid 98x RISC machine.
I ran adb on this program, but the messages it gave me were cryptic.

-- 
Neal R. Vanderlipp 	
ARPA:	neal@maryland
CSNet:	neal@umcp-cs 		
UUCP:	{seismo,allegra}!umcp-cs!neal

neal@gymble.UUCP (Neal R. Vanderlipp) (08/17/85)

>> My program crashed. Can anyone debug it for me? Here's the core dump:
>> 
>> 0000000  000000 000000 000000 000000 000000 000000 000000 000000
>> 0000020  000000 000000 000000 000000 000000 000000 000000 000000
>	...
>> 0000760  000537 000400 000000 000400 000000 000012 000000 000377
>> 0001000  177777 177777 177777 177777 177777 177777 177777 177777
>> 0001020  177777 177777 000537 000400 000000 000000 177600 007770
>> 0001040  177600 007724 017765 011600 177404 105230 000000 000002	<<-
>	...
>
>It's quite simple.  The line in your program which reads
>
> 	if (FF<&_flf[0]||FF>=&_flf[NFLF]||FF!=&_flf[FF-&_flf[0]]||FF->ff_dir==NULL){radon(bad_flf,67);return foo->ff_bc = getbch(dptr->di_ack,dptr->di_tor);}
>
>should read
>
>	if (FF<&_flf[0]||FF>=&_flf[NFLF]||FF!=&_flf[FF-&_flf[0]]||FF->ff_dir==NULL){radon((bad_flf,67));return foo->ff_bc = getbch(dptr->di_ack,dptr->di_tor);}
>
>Glad to help!
>
>--
>John Woods, Charles River Data Systems, Framingham MA, (617) 626-1101

Thanks John, that looks like it will probably work, but I'm looking for
a solution which is not load dependent.

-- 
Neal R. Vanderlipp 	
ARPA:	neal@maryland
CSNet:	neal@umcp-cs 		
UUCP:	{seismo,allegra}!umcp-cs!neal