filePro 32-bit binaries segv on CentOS 64-bit

[Bob Rasmussen]

My recollection, long dusty, is that this is a limit in the library 
routines that process the termcap. I know I've run in to this before, 
totally unrelated to filePro. In that situation, as here, the solution was 
to shorten the termcap entry.

I believe I also recall that the TERM environment variable can contain 
EITHER the name of the termcap entry in the /etc/termcap (or similar) 
file, or the entire, literal entry. Obviously it is the latter that 
encounters the problem.

I wonder if the authors of 'screen' encountered this problem and changed 
their approach between the two versions cited.

On Wed, 19 Feb 2014, Fairlight wrote:

> On Wed, Feb 19, 2014 at 10:55:21AM -0500, Kenneth Brody thus spoke:
>> Termcap entries are (or, at least "were") limited to 1024
>> characters.  The one that screen sets in the environment is 1227
>> characters.
>>
>> As a quick test, I modified the value to make it 1000 characters,
>> and I now get the expected "terminal type not found" error.
>
> Well, that explains that.
>
> So is it fP coughing, or libtermcap?  At this point, it's academic, but it
> would be nice to know.
>
> m->
> -- 
> Audio panton, cogito singularis.
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>

Regards,
....Bob Rasmussen,   President,   Rasmussen Software, Inc.

personal e-mail: ras at anzio.com
  company e-mail: rsi at anzio.com
           voice: (US) 503-624-0360 (9:00-6:00 Pacific Time)
             fax: (US) 503-624-0760
             web: http://www.anzio.com
  street address: Rasmussen Software, Inc.
                  10240 SW Nimbus, Suite L9
                  Portland, OR  97223  USA