tiny-cobol-users

Re: [Tiny-cobol-users] Segmentation Fault - unable to trace

[<ra...@gr...>]

Hi David,

I did try to debug as mentioned by you. But still no clue. Any luck with you?

TIA
Ravi

On Fri, 15 Jul 2005 02:27 , David Essex <de...@us...> sent:

>ravi :
>
> > Could someone pls help me with the following?
> > I am able to compile the programs without any error.
> > But I get "segmentation fault" on executing the binary.
> > One is calling program and the other called program.
> > gdb is also of no use in this case. I am unable to
> > proceed any further. Pls help.
> > I have attached both the programs in one single file.
>
>There is some sort of memory corruption problem in one of the literals 
>or identifiers.
>
>This is causing a segmentation fault when one of the identifiers gets 
>initialized due to the VALUE clause.
>
>Due to the large amount of literals and identifiers it is difficult to 
>isolate the problem, as the memory location where the problem occurs may 
>have only a casual relation to the problem.
>And since the memory location is corrupt, it is difficult, if not 
>impossible, to identify the problem statement.
>
>Anyway I will try to isolate the problem.
>
>BTW, if you which to look at the problem just compile the run-time with 
>the GCC '-g' option, and set the '.gdbinit' file with a break-point at 
>'b tcob_move'.
>The run the tests program (gdb BPVITD3), and use the continue command.
>
>
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>from IBM. Find simple to follow Roadmaps, straightforward articles,
>informative Webcasts and more! Get everything you need to get up to
>speed, fast. http://ads.osdn.com/\?ad_id=7477&alloc_id=16492&op=click
>_______________________________________________
>Tin...@li...
>https://lists.sourceforge.net/lists/listinfo/tiny-cobol-users

Re: [Tiny-cobol-users] Segmentation Fault - unable to trace

[David E. <de...@us...>]

ravi wrote:

> I did try to debug as mentioned by you. 
 > But still no clue. Any luck with you?

No real progress.

The problem occurs with on the following statement.

05 IT-PARTY-TOT-O PIC Z(10).ZZ VALUE ZEROES.

When the identifier 'IT-PARTY-TOT-O' gets initialized by the figurative 
constant (literal) ZEROES.

Unfortunately part of the literal structure memory is corrupt, and the 
data location pointer does not seam to point to the correct contents.

If I try to duplicate the problem with a smaller program with the above 
statement, then the problem does not occur.

Re: [Tiny-cobol-users] Segmentation Fault - unable to trace

[Rildo P. <ri...@pr...>]

Hi Ravi,

ra...@gr... wrote:

>Hi David,
>
>I did try to debug as mentioned by you. But still no clue. Any luck with you?
>
>  
>
I found why the bug happens! The problem is with processing OCCURS in 
level 01 data items.
I suggest a workaround like this (according your code):

       01  date-table.
        02  date-table-reg occurs 20 times.
           05  dt-bk-cd                 pic 99.
           05  dt-memo-amt              pic s9(10)v99
                 sign leading separate.

Please, report me any other bugs found. I'm trying to make our compiler 
usable.

>TIA
>Ravi
>
>On Fri, 15 Jul 2005 02:27 , David Essex <de...@us...> sent:
>
>  
>
>>ravi :
>>
>>    
>>
>>>Could someone pls help me with the following?
>>>I am able to compile the programs without any error.
>>>But I get "segmentation fault" on executing the binary.
>>>One is calling program and the other called program.
>>>gdb is also of no use in this case. I am unable to
>>>proceed any further. Pls help.
>>>I have attached both the programs in one single file.
>>>      
>>>
>>There is some sort of memory corruption problem in one of the literals 
>>or identifiers.
>>
>>This is causing a segmentation fault when one of the identifiers gets 
>>initialized due to the VALUE clause.
>>
>>Due to the large amount of literals and identifiers it is difficult to 
>>isolate the problem, as the memory location where the problem occurs may 
>>have only a casual relation to the problem.
>>And since the memory location is corrupt, it is difficult, if not 
>>impossible, to identify the problem statement.
>>
>>Anyway I will try to isolate the problem.
>>
>>BTW, if you which to look at the problem just compile the run-time with 
>>the GCC '-g' option, and set the '.gdbinit' file with a break-point at 
>>'b tcob_move'.
>>The run the tests program (gdb BPVITD3), and use the continue command.
>>
>>
>>
>>
>>-------------------------------------------------------
>>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>>    
>>
>>from IBM. Find simple to follow Roadmaps, straightforward articles,
>  
>
>>informative Webcasts and more! Get everything you need to get up to
>>speed, fast. http://ads.osdn.com/\?ad_id=7477&alloc_id=16492&op=click
>>_______________________________________________
>>Tin...@li...
>>https://lists.sourceforge.net/lists/listinfo/tiny-cobol-users
>>    
>>
>
>
>
>
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>from IBM. Find simple to follow Roadmaps, straightforward articles,
>informative Webcasts and more! Get everything you need to get up to
>speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>_______________________________________________
>Tin...@li...
>https://lists.sourceforge.net/lists/listinfo/tiny-cobol-users
>
>  
>

best regards,
Rildo

-- 
 ------------------------------------------------------------------
 Rildo Pragana                   FPGA/uControllers * Linux * tcl/tk
 R.Joaquim Nabuco,92/1102 Derby  http://www.pragana.net
 Recife, PE - Brazil 52011-000   +55-81-3223-5694  / 8837-6122