From: Richard Hirst <rhirst@linuxcare.com>
To: Greg Ingram <ingram@symsys.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] C100 improvements, problems
Date: Sun, 4 Feb 2001 12:11:06 +0000 [thread overview]
Message-ID: <20010204121106.A1374@linuxcare.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0101261205420.31352-100000@maestro.symsys.com>; from ingram@symsys.com on Fri, Jan 26, 2001 at 12:16:29PM -0600
On Fri, Jan 26, 2001 at 12:16:29PM -0600, Greg Ingram wrote:
> > There is a bug in more (really!), now fixed, but needs a rebuild. If you
> > invoke it as /bin/more you'll be ok.
>
> I believe it, I just don't believe it. Is this related to stack
> direction? (What is it: grows down on parisc but up on Intel and most
> other Linux-supported processors?) If so, what is more fiddling with on
> its stack? Does it alter its behavior based on argv[0]? Oh well, not
> really too important now, I guess.
parsic grows up, most others grow down. 'more' checked argv[0] to see
how it was invoked, and due to a coding bug tried to read argv[0][-1].
As argv[0] is the first item on our stack, that caused a trap.
Richard
next prev parent reply other threads:[~2001-02-04 13:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 3:46 [parisc-linux] 2.4.0 merge mangle our tree? Grant Grundler
2001-01-25 4:19 ` Michael Ang
2001-01-25 13:02 ` Matthew Wilcox
2001-01-25 14:56 ` Michael Ang
2001-01-25 15:06 ` Matthew Wilcox
2001-01-25 10:19 ` Richard Hirst
2001-01-25 12:00 ` Richard Hirst
2001-01-25 17:33 ` [parisc-linux] C100 improvements, problems Greg Ingram
2001-01-25 17:36 ` Richard Hirst
2001-01-26 18:16 ` Greg Ingram
2001-02-04 12:11 ` Richard Hirst [this message]
2001-01-25 17:42 ` Matthew Wilcox
2001-01-26 18:17 ` [parisc-linux] C100 report, latest CVS bits Greg Ingram
2001-01-25 18:24 ` [parisc-linux] 2.4.0 merge mangle our tree? Grant Grundler
2001-01-25 17:24 ` Matthew Wilcox
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=20010204121106.A1374@linuxcare.com \
--to=rhirst@linuxcare.com \
--cc=ingram@symsys.com \
--cc=parisc-linux@thepuffingroup.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.