Re: [Tiny-cobol-users] Segmentation Fault

[Reg <re...@ri...>]

Hi David,
After messing around with various alternatives, I decided that passing
multiple large linkage parameters from program to program was too flakey, so
now write them to a file and read them with single programs each compiled
with -x and running separately.
Works fine, segmentation errors gone.
Problem now is that lockserver doesn't work.
Set lockserver running in -d mode, comes up with messages ending with
"Server socket set-up" so seems to be running fine.
Re-did Tiny Cobol config in development directory with --enable-lockserv,
make, make install. Seems to completely ignore the option. No reference to
it in config.log, compiler chucks out error message on encountering "unlock"
(undefined reference to tcob_unlock), no locking taking place on "read with
lock" according to lockserver debug, no lock (status 51) encountered when
expected in programs..
What am I doing wrong?
Regards,
Reg.
PS Sorry to hear that you intend to "retire" from the TC project next year,
but I guess you have done more than your share........ I for one am grateful
for your efforts.
Thanks.
Reg.



David Essex-2 wrote:
> 
> Reg wrote:
> 
>  > Next problem:-
>  > Whether I compile with -m and run vis htcobrun or
>  > compile with -x for an executable,
>  > when I call the next program in the system I get:-
>  >
>  > /TinyCat/startpass1: line 4: 13359 Segmentation fault
>  > /TinyCobol/development/cobrun/htcobrun PASSCHEC1
>  >
>  > (different number for fault from -x version).
>  > This seems to occur when PASSCHEC1 calls the next
>  > program, which was compiled with -m.
>  > Could be the next program is large or the single
>  > parameter passed in linkage is too big?
>  > Anyway, seems like a memory fault similar to the
>  > compile problem prior to the CVS version.
> 
> I don't have sufficient information to determine the problem.
> 
> But usually a 'segmentation fault' with a CALL statement usually occurs 
> when the input/output paramaters are not in sync.
> Or when a dynamic call fails and input/output paramater data contains
> junk.
> 
> Did you set the following 'environment variables' ?
> 
> export TCOB_LD_LIBRARY_PATH=/TinyCat
> export LD_LIBRARY_PATH=/TinyCat
> 
> Hint:
> You can check a call statement with the following code.
> CALL ... ON EXCEPTION ...
> 
> Cheers.
> 
> 
> 
> -------------------------------------------------------------------------
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services
> for just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Tin...@li...
> https://lists.sourceforge.net/lists/listinfo/tiny-cobol-users
> 
> 

-- 
View this message in context: http://www.nabble.com/Segmentation-Fault-tp12496784p14471041.html
Sent from the tiny-cobol-users mailing list archive at Nabble.com.