From: Albert Cahalan <albert@users.sourceforge.net>
To: linas@austin.ibm.com
Cc: Albert Cahalan <albert@users.sourceforge.net>,
linuxppc-dev@lists.linuxppc.org, benh@kernel.crashing.org
Subject: Re: 64-bit user-space on G5? Never, soonish, or unknown?
Date: 01 Mar 2004 18:42:42 -0500 [thread overview]
Message-ID: <1078184561.2255.338.camel@cube> (raw)
In-Reply-To: <20040301163844.G74832@forte.austin.ibm.com>
On Mon, 2004-03-01 at 17:38, linas@austin.ibm.com wrote:
> On Sat, Feb 28, 2004 at 06:16:28PM -0500, Albert Cahalan wrote:
> > You'd better have a 64-bit ncurses. If you don't,
> > your procps will be compiled incorrectly. Data
> > will get truncated, mangled, etc. -- assuming you
> > can even run the tools at all.
>
> ? My ps, top, w all work fine:
>
> linas@panic:~> file /usr/bin/top
> /usr/bin/top: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV), dynamically linked (uses shared libs), stripped
> linas@panic:~> file /bin/ps
> /bin/ps: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV), dynamically linked (uses shared libs), stripped
>
> They've been running fine, with all manner of mangled and hacked
> 2.4 and 2.6 kernels.
Try this:
ps -eo drs,trs,tsiz,dsiz,start_stack,esp,eip,nwchan,wchan
(especially when examining a 64-bit process or when
running on the 2.4 kernel)
By "assuming you can run the tools at all" I mean that
you might end up with 32-bit libraries in /lib64.
If you build on a pure 32-bit system this won't happen.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-01 23:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 23:16 64-bit user-space on G5? Never, soonish, or unknown? Albert Cahalan
2004-03-01 22:38 ` linas
2004-03-01 23:42 ` Albert Cahalan [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-12 7:49 Mikael Pettersson
2004-02-12 7:47 Mikael Pettersson
2004-02-11 14:09 Mikael Pettersson
2004-02-11 14:51 ` Christian Kujau
2004-02-11 15:33 ` tom_gall
2004-02-11 22:14 ` Benjamin Herrenschmidt
2004-02-11 22:26 ` Anton Blanchard
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=1078184561.2255.338.camel@cube \
--to=albert@users.sourceforge.net \
--cc=benh@kernel.crashing.org \
--cc=linas@austin.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).