From: Ralf Baechle <ralf@linux-mips.org>
To: Don Hiatt <Don_Hiatt@pmc-sierra.com>
Cc: "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: Trival shell script crashes under 2.4.25
Date: Thu, 15 Sep 2005 20:17:47 +0100 [thread overview]
Message-ID: <20050915191747.GT3224@linux-mips.org> (raw)
In-Reply-To: <5C1FD43E5F1B824E83985A74F396286E5E9475@bby1exm08.pmc_nt.nt.pmc-sierra.bc.ca>
On Wed, Sep 14, 2005 at 04:00:40PM -0700, Don Hiatt wrote:
> Sorry if this is the wrong list to post to; if it is, could you
> please suggest an alternative? :)
How about linux-mips ;-)
> Below you will find a very simple shell script that crashes under
> 2.4.25 running on a RM9000 (PMC rm7935) with busybox 1.0. This script
> just demonstrates the actual problem but I do not believe it is
> isolated to busybox. In fact I wrote a simple program that just does
> this:
> * for(;;)
> * fork()
> * mmap file "foo"
> * compare "foo" to an array image
> * waitpid()
linux-mips.org has no RM9000 support in it's 2.4 code. That leaves
it up to guessing what could be happening in your codebase.
> and it will run for a while and then SEGFAULT at various times. According
> to GDB the stack is corrupted and looking at the PC it does seem bogus
> (0x2acf2e50).
That would be a typical address for a shared library.
> The program crashes after a random amount of time but generally no more
> that a minute or so. I can speed up the process if I ping-flood the target.
>
> Now what is really wierd is that if I run the program under gdbserver
> it doesn't crash (or at least has not in the last 1/2 hour). Does gdbserver
> change the execution context differently that gdb??
Strange indeed. Both shouldn't affect the state of a running program
as long as it isn't being stopped.
Ralf
prev parent reply other threads:[~2005-09-15 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 23:00 Trival shell script crashes under 2.4.25 Don Hiatt
2005-09-15 19:17 ` Ralf Baechle [this message]
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=20050915191747.GT3224@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Don_Hiatt@pmc-sierra.com \
--cc=linux-mips@linux-mips.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 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.