| To: | Martin Michlmayr <tbm@cyrius.com> |
|---|---|
| Subject: | Re: 1480: "bad address" instead of "argument list too" |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Fri, 17 Mar 2006 17:02:42 +0000 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <20060317165629.GX18750@deprecation.cyrius.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <20060317165629.GX18750@deprecation.cyrius.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4.2.1i |
On Fri, Mar 17, 2006 at 04:56:29PM +0000, Martin Michlmayr wrote: > I get the following in a directory which has many files in it on a > Braodcom 1480: > > 2179:tbm@bigsur: ~/build/logs] grep foo * > zsh: bad address: grep > > Normally, I'd expect an "zsh: argument list too long: grep" error. > > I get this with different shells. Hmm, that's interesting. "echo *" > works. I assume shell built-in commands work but others don't. Chances are this is caused by the return value of some syscall. Can you use strace on a shell to isolate it? Is this 32-bit software on a 64-bit kernel? Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | 1480: "bad address" instead of "argument list too", Martin Michlmayr |
|---|---|
| Next by Date: | Re: 1480: "bad address" instead of "argument list too", Martin Michlmayr |
| Previous by Thread: | 1480: "bad address" instead of "argument list too", Martin Michlmayr |
| Next by Thread: | Re: 1480: "bad address" instead of "argument list too", Martin Michlmayr |
| Indexes: | [Date] [Thread] [Top] [All Lists] |