From: Venkatesh Ramamurthy <Venkateshr@ami.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Issue with using execlp() from a 32 bit binary on IA64
Date: Thu, 13 Sep 2001 18:14:43 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805175@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]
Hi,
The RAID group has a problem with using execlp function from a 32bit binary.
The problem goes like this , a test program "TestCtrl"(A) and "TestServ"(B)
are the two binaries. Initially both 'A' and 'B' are 32 bit binaries. 'A'
loads 'B' using execlp. 'A' loads during system startup. The system boots to
text mode. When i do a 'startx', the X-window system hangs up. The last
thing i see is 'RAGE 128 .....' and hangs.
When i recompile A to a native 64 bit app everything is fine (B is still 32
bit app). X - Window runs fine.
So my assumption was when a 32 bit binary spawns another 32bit app(i have
*not* tested a 32 bit app loading a 64 bit app) there is a problem, I have
not gone thru the kernel sources to find the source of the error. As i am
not actively involved with Linux64 development i do not have time to study
the problem more, but i thought it might be useful for the maintainers to
rectify it.
I am sending the sources and some readme documents from one of our engineers
in India who orginated this issue. He is seeing it in a slightly different
manner.He states that even when 'A' is natively compiled he sees the
problem. We have not seen this in atlanta.
Hope this helps ....
Thanks
Venkatesh
PS: I receive only the digest so please CC communication and also include
peterj in the loop.
<<testmon.tar.gz>>
[-- Attachment #2: testmon.tar.gz --]
[-- Type: application/octet-stream, Size: 7851 bytes --]
next reply other threads:[~2001-09-13 18:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-13 18:14 Venkatesh Ramamurthy [this message]
2001-09-13 19:11 ` [Linux-ia64] Issue with using execlp() from a 32 bit binary on IA64 Brian Sumner
2001-09-14 10:17 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ia64-105590698805175@msgid-missing \
--to=venkateshr@ami.com \
--cc=linux-ia64@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox