Sponsored Content
Top Forums Programming Seg Fault Running AIX COBOL program Post 302279314 by jim mcnamara on Thursday 22nd of January 2009 11:23:10 AM
Old 01-22-2009
If it runs correctly on the previous "release", the code has not changed, the data has not changed, the inputs have not changed, and it fails to run when recompiled, it is most likely related to runtime libraries. Was the cobol runtime support library "patched" or updated? What does the vendor website say about compatibility of code going forward?

I'm the one who gets to work on problems like this, but not in AIX. The OS guys are thinking you did something "special" with this module. COBOL doesn't do "special" very well. Or very portably either.
 

10 More Discussions You Might Find Interesting

1. Programming

Open Suse 10 seg fault

Okay, so here is some code that when compiled on Fedora Core 6 works great, but when I compile and run it on OpenSuse 10 it gives back a seg fault when trying to join the 2nd thead. #include <pthread.h> #include <stdio.h> int print_message_function( void *ptr ); int x = 1; main() { ... (1 Reply)
Discussion started by: chrisdrobison
1 Replies

2. HP-UX

HP-UX 64 compilation causing some code to seg fault

Hello everyone, Today we are attempting to port some legacy C code to a 64 HP-UX machine at my company and there is kind of a strange error we ran into. there is a small function they have defined called zgetenv that accepts a char* and basically just does some null checking and returns ... (0 Replies)
Discussion started by: khadesh
0 Replies

3. Programming

How to debug with wdb debugger a cobol program?

Hi Forum, i have such a question. I have a cobol program which is calling a C program and in that C program i get a core dump:(. I want to investigate what is the issue using WDB debuger, but a dont see the code from COBOL program in the debuger, when i run the debugger with the exe!!! ... (2 Replies)
Discussion started by: vovan
2 Replies

4. Programming

cobol crn programme run on express cobol as .gnt

can i run .crn programme in express cobol which support to .gnt programme .... Plz tell me solution (2 Replies)
Discussion started by: bibi
2 Replies

5. Programming

Xlib Problem: XCloseDisplay seg fault

Hi, First of all forgive me if Xlib related problems does not go under this thread. In my main program, im using Xlib`s XImage type object which contains a regularly updating bitmap, and maps the XImage to a Xwindow using XPutImage. ( XCreateImage is used to create the XImage. ) The... (0 Replies)
Discussion started by: wolwy_pete
0 Replies

6. Shell Programming and Scripting

Calling script from RM cobol and returning value to cobol

Is there a way you can return a value from a script that is called from a rm cobol program... 01 WS-COMD-LINE-PGM X(39) value sh ./getUserId.sh 12345" 01 WS-RETURN-SYS-CODE PIC 9(8). CALL "SYSTEM" USING WS-COMD-LINE-PGM GIVING WS-RETURN-SYS-CODE. ... (1 Reply)
Discussion started by: pavanmp
1 Replies

7. Programming

Acceessing DB2 UDB in AIX COBOL on unix

Hi , We are migrating our database from DB2 z/os to DB2 UDB on UNIX. and cobol on mainframes to AIX cobol on UNIX. We have some cobol Db2 programs that are accessing different Databases how do we code such type of programs in AIX cobol. Do we need to Establish connection for accessing... (0 Replies)
Discussion started by: nal.satish
0 Replies

8. UNIX for Advanced & Expert Users

Running C#.NET program in AIX?

Hi Guys Am new in UNIX environment I was asked by my boss to write a program that transfer files from the AIX server to the Wintel Server. I have written the program in C# windows which does almost the same thing. So how to run the C# program in UNIX? (1 Reply)
Discussion started by: michmsk
1 Replies

9. AIX

Urgent!! Debugging tool for cobol in AIX

hi folks, I am a new to Aix, i worked as sys admin so no idea about software probs, my software team requires Debugging tool for cobol in AIX machine. can someone tell me the tool and also the installation procedure for the same Please drag me out from this soon :confused: (1 Reply)
Discussion started by: atulgkwd
1 Replies

10. Shell Programming and Scripting

Can a shell variable be called in a cobol program

Hi All, I have a file which sets all the variables on unix , based on the hostname. Currently these variables are hardcoded in the cobol programs.I was wondering if unix variables can be used in Cobol programs ? Example : I have a variable $SHTEMP which is set based on the following : Prod... (2 Replies)
Discussion started by: nua7
2 Replies
Lexical::SealRequireHints(3)				User Contributed Perl Documentation			      Lexical::SealRequireHints(3)

NAME
Lexical::SealRequireHints - prevent leakage of lexical hints SYNOPSIS
use Lexical::SealRequireHints; DESCRIPTION
This module works around two historical bugs in Perl's handling of the "%^H" (lexical hints) variable. One bug causes lexical state in one file to leak into another that is "require"d/"use"d from it. This bug, [perl #68590], was present from Perl 5.6 up to Perl 5.10, fixed in Perl 5.11.0. The second bug causes lexical state (normally a blank "%^H" once the first bug is fixed) to leak outwards from "utf8.pm", if it is automatically loaded during Unicode regular expression matching, into whatever source is compiling at the time of the regexp match. This bug, [perl #73174], was present from Perl 5.8.7 up to Perl 5.11.5, fixed in Perl 5.12.0. Both of these bugs seriously damage the usability of any module relying on "%^H" for lexical scoping, on the affected Perl versions. It is in practice essential to work around these bugs when using such modules. On versions of Perl that require such a workaround, this module globally changes the behaviour of "require", including "use" and the implicit "require" performed in Unicode regular expression matching, so that it no longer exhibits these bugs. The workaround supplied by this module takes effect the first time its "import" method is called. Typically this will be done by means of a "use" statement. This should be done as early as possible, because it only affects "require"/"use" statements that are compiled after the workaround goes into effect. For "use" statements, and "require" statements that are executed immediately and only once, it suffices to invoke the workaround when loading the first module that will set up vulnerable lexical state. Delayed-action "require" statements, however, are more troublesome, and can require the workaround to be loaded much earlier. Ultimately, an affected Perl program may need to load the workaround as very nearly its first action. Invoking this module multiple times, from multiple modules, is not a problem: the workaround is only applied once, and applies to everything subsequently compiled. This module is implemented in XS, with a pure Perl backup version for systems that can't handle XS modules. The XS version has a better chance of playing nicely with other modules that modify "require" handling. The pure Perl version can't work at all on some Perl versions; users of those versions must use the XS. PERL VERION DIFFERENCES
The history of the "%^H" bugs is complex. Here is a chronological statement of the relevant changes. Perl 5.6.0 "%^H" introduced. It exists only as a hash at compile time. It is not localised by "require", so lexical hints leak into every module loaded, which is bug [perl #68590]. The "CORE::GLOBAL" mechanism doesn't work cleanly for "require", because overriding "require" loses the necessary special parsing of bareword arguments to it. As a result, pure Perl code can't properly globally affect the behaviour of "require". Pure Perl code can localise "%^H" itself for any particular "require" invocation, but a global fix is only possible through XS. Perl 5.7.2 The "CORE::GLOBAL" mechanism now works cleanly for "require", so pure Perl code can globally affect the behaviour of "require" to achieve a global fix for the bug. Perl 5.8.7 When "utf8.pm" is automatically loaded during Unicode regular expression matching, "%^H" now leaks outward from it into whatever source is compiling at the time of the regexp match, which is bug [perl #73174]. It often goes unnoticed, because [perl #68590] makes "%^H" leak into "utf8.pm" which then doesn't modify it, so what leaks out tends to be identical to what leaked in. If [perl #68590] is worked around, however, "%^H" tends to be (correctly) blank inside "utf8.pm", and this bug therefore blanks it for the outer module. Perl 5.9.4 "%^H" now exists in two forms. In addition to the relatively ordinary hash that is modified during compilation, the value that it had at each point in compilation is recorded in the compiled op tree, for later examination at runtime. It is in a special representation- sharing format, and writes to "%^H" are meant to be performed on both forms. "require" does not localise the runtime form of "%^H" (and still doesn't localise the compile-time form). A couple of special "%^H" entries are erroneously written only to the runtime form. Pure Perl code, although it can localise the compile-time "%^H" by normal means, can't adequately localise the runtime "%^H", except by using a string eval stack frame. This makes a satisfactory global fix for the leakage bug impossible in pure Perl. Perl 5.10.1 "require" now properly localises the runtime form of "%^H", but still not the compile-time form. A global fix is once again possible in pure Perl, because the fix only needs to localise the compile-time form. Perl 5.11.0 "require" now properly localises both forms of "%^H", fixing [perl #68590]. This makes [perl #73174] apparent without any workaround for [perl #68590]. The special "%^H" entries are now correctly written to both forms of the hash. Perl 5.12.0 The automatic loading of "utf8.pm" during Unicode regular expression matching now properly restores "%^H", fixing [perl #73174]. BUGS
The operation of this module depends on influencing the compilation of "require". As a result, it cannot prevent lexical state leakage through a "require" statement that was compiled before this module was invoked. Where problems occur, this module must be invoked earlier. SEE ALSO
perlpragma AUTHOR
Andrew Main (Zefram) <zefram@fysh.org> COPYRIGHT
Copyright (C) 2009, 2010, 2011, 2012 Andrew Main (Zefram) <zefram@fysh.org> LICENSE
This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.18.2 2017-10-06 Lexical::SealRequireHints(3)
All times are GMT -4. The time now is 04:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy