- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- 32/64-bit portabliity
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2006 04:03 AM
06-21-2006 04:03 AM
32/64-bit portabliity
When I try and run it on a HP-UX 11.00 box with 32-bit O/S anything using curses fails (coredump SIGSEGV). But anything not using curses works OK.
All the libraries I have used/linked are PARISC1.1
Any clues?
- Tags:
- SIGSEGV
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2006 04:17 AM
06-21-2006 04:17 AM
Re: 32/64-bit portabliity
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2006 04:20 AM
06-21-2006 04:20 AM
Re: 32/64-bit portabliity
- Tags:
- ncurses
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2006 05:03 AM
06-21-2006 05:03 AM
Re: 32/64-bit portabliity
Did you compile with ncurses of 64 bit (PA-RISC1.1) ? Jus a thought i should say ..
-Arun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2006 05:09 AM
06-21-2006 05:09 AM
Re: 32/64-bit portabliity
The other thing that might cause problems is that if ncurses were compiled with one set of header files and your application were compiled with another slightly different set of header files.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-21-2006 05:09 AM
06-21-2006 05:09 AM
Re: 32/64-bit portabliity
You need to recompile for higher platforms.
Once you do that, you should be able to maintain 32 and 64 bit versions. I'm told 11 v2's 32 bit emulation solves a lot of problems when compared to other earlier OS versions.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2006 01:49 AM
06-22-2006 01:49 AM
Re: 32/64-bit portabliity
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2006 03:18 AM
06-27-2006 03:18 AM
Re: 32/64-bit portabliity
Does anyone have ncurses running successfully on 32-bit HP-UX 11.00, and if so
(a) what version of ncurses is it and
(b) where did they get it from please?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2006 01:03 PM
06-27-2006 01:03 PM
Re: 32/64-bit portabliity
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2006 01:52 PM
06-27-2006 01:52 PM
Re: 32/64-bit portabliity
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2006 09:02 PM
06-27-2006 09:02 PM
Re: 32/64-bit portabliity
/usr/lib/libc.2
/usr/lib/libdld.2
/usr/lib/libm.2
/usr/local/lib/libstdc++.sl
I'll see if I can get hold of a stack trace, as I feel a weakness in the force.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2006 08:18 PM
06-29-2006 08:18 PM
Re: 32/64-bit portabliity
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2006 08:51 AM
06-30-2006 08:51 AM
Re: 32/64-bit portabliity
#0 0x0004702c in postprocess_termcap ()
#1 0x00046678 in _nc_parse_entry ()
#2 0x0003fd68 in _nc_read_entry_source ()
#3 0x0003b6b8 in _nc_read_termcap_entry ()
#4 0x0002baf0 in grab_entry ()
#5 0x0002bfd0 in _nc_setupterm ()
#6 0x0002c1c8 in setupterm ()
#7 0x00030ae4 in newterm ()
#8 0x00025380 in initscr ()
Cannot access memory at address 0xffffea6d
Definitely the ncurses5.5 library that is core-dumping then.
Why is it using a termcap function, I though ncurses preferred terminfo entries?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2006 09:18 AM
06-30-2006 09:18 AM
Re: 32/64-bit portabliity
Actually they may be a few cases where termcap makes sense because unlike terminfo, terminfo can deal with completely ad hoc capability names that you make up yourself. The terminfo compiler would choke on a madeup capability name.
I suspect that you may be running on boxes which do not have matching terminfo entries but do have matching termcap entries and the fallback is what is killing you and why it works on some boxes and doesn't on others. The OS "bitness" probably has nothing to do with it.
Amazingly now that I have a stack trace, "The Force" seems stronger.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2006 09:27 AM
06-30-2006 09:27 AM
Re: 32/64-bit portabliity
I have TERM=vt100
I have TERMINFO=/usr/share/terminfo
I have /usr/local/share/terminfo/v/vt100
I have /usr/share/lib/terminfo/v/vt100
I have also tried TERM=vt220, TERM=hp etc.
How do I configure ncurses to not use TERMCAP for instance?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2006 09:47 AM
06-30-2006 09:47 AM
Re: 32/64-bit portabliity
Also make sure that your application code isn't being compiled with one set of header files
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2006 09:55 AM
06-30-2006 09:55 AM
Re: 32/64-bit portabliity
Presumably the ncurses library will throw an error if it can't find a suitable terminfo, as I've asked it not to fall-back on termcap?
I'm also getting a copy of the terminfo files from the "problem" server to see if I can "break" my system by using them. If I could only get it to break here, I'd be one step closer to fixing it!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2006 10:14 AM
06-30-2006 10:14 AM
Re: 32/64-bit portabliity
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2006 01:11 AM
07-01-2006 01:11 AM
Re: 32/64-bit portabliity
Is there a quick way to verify the terminfo database files?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2006 02:10 PM
07-01-2006 02:10 PM
Re: 32/64-bit portabliity
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2006 09:25 PM
07-02-2006 09:25 PM
Re: 32/64-bit portabliity
The application is statically linked with the ncurses archive libraries. There are no ncurses shared libraries on the target machine. Also, perhaps more importantly, there are no ncurses binaries on the target machine, it uses the HP supplied variants of clear/infocmp/tic/toe/tput/tset etc. so the target machine has HP terminfo databases and HP term habdling binaries.
I've been experimenting with setting TERMINFO and TERMCAP, but it doesn't seem to make any difference.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2006 09:39 PM
07-02-2006 09:39 PM
Re: 32/64-bit portabliity
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2006 01:12 AM
07-05-2006 01:12 AM
Re: 32/64-bit portabliity
If TERMINFO is not set, you get an error message. If TERMINFO is set (correctly) the application works fine.
Just to check, I then recompiled the ncurses sources without --disable-termcap and ran the application.
If TERMINFO is not set you don't (now) get a core-dump, you get an error message about "Name collision between h hh" etc. IF TERMINFO is set (correctly) the application works fine.
So unless the orginal ncurses build was somehow corrupted, I don't get it. But I have an application that works and I'm seeing if it works on the 32-bit version of 11.00 too.