From: "Chetan Kapoor" <chetan.kapoor@flextronicssoftware.com>
To: linux-omap-open-source@linux.omap.com
Subject: Re: init (busybox) problem on OSK5912
Date: Wed, 10 May 2006 13:08:23 +0530 [thread overview]
Message-ID: <14fc2db60605100038t7c95cd6ag18d2ee592ca1bbf@mail.gmail.com> (raw)
Hi,
I have made some findings to resolve this issue. May be this is helpful for you.
We were also facing the similar issue where the gdbserver when linked
dynamically was always resulting in a segmentation fault. We have
ensured that the version of libraries used while compilation are same
in the target also. But still , the gdbserver was resulting in a crash
(always before accept system call).
After going through other mailing lists, I have found that this issue
is happening because of a bug in glibc libraries. I have rebuilt the
glibc libraries (2.3.5 version) for arm after deleting the
sysdeps/arm/memset.S file. I have used the newly built "libc.so.6" and
"ld-linux.so.2" for compilation and runtime environment. This time
gdbserver and other dynamically shared program worked fine.
May be you can give this step a try. I have followed the steps for
building toolchain from http://frank.harvard.edu/~coldwell/toolchain/
Regards,
Dinesh
++ Sent by Chetan Kapoor on behalf of Dinesh Arora ++
*********************** FSS-Unclassified ***********************
next reply other threads:[~2006-05-10 7:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 7:38 Chetan Kapoor [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-10 7:21 init (busybox) problem on OSK5912 chetan.kapoor
2006-05-10 7:08 Chetan Kapoor
2006-05-04 7:19 Fw: " Chetan Kapoor
2006-05-04 7:59 ` Eduardo Gallofin
[not found] <20060503194919.7EDC38062D@linux.omap.com>
2006-05-04 6:47 ` Eduardo Gallofin
2006-05-04 16:43 ` andrzej zaborowski
2006-05-05 0:10 ` Eduardo Gallofin
2006-05-05 2:39 ` Eduardo Gallofin
[not found] <20060501170002.24B3A8062B@linux.omap.com>
2006-05-02 7:09 ` Eduardo Gallofin
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=14fc2db60605100038t7c95cd6ag18d2ee592ca1bbf@mail.gmail.com \
--to=chetan.kapoor@flextronicssoftware.com \
--cc=linux-omap-open-source@linux.omap.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox