All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theo Gjaltema <gjalt007@chello.nl>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Dynamic libraries do not work
Date: Fri, 27 May 2005 07:36:18 +0200	[thread overview]
Message-ID: <4296B1D2.5090409@chello.nl> (raw)
In-Reply-To: <528646bc05052615304d896b94@mail.gmail.com>

Grant Likely schreef:

>On 5/26/05, Theo Gjaltema <gjalt007@chello.nl> wrote:
>  
>
>>Hello,
>>
>>I have a linux 2.4.20 kernel running, but the files in the ramdisk fail
>>to execute if they are dynamically build.
>>The whole system stops (debuggers shows that it crashed while in an erea
>>where no flash/ram is present.
>>Anyone an idea?
>>There is nog difference between the use of a ramdisk or an nfs mounted
>>root filesystem.
>>
>>    
>>
>More data please;  Make sure you attach actual output when asking for help.
>
>  
>
You are right, this gives too little info. Since the system stops 
without giving any data, I don't know what to attach
maybe:
RAM: 64 Mbyte

(using a static linked busybox: activating a sh (=busybox) b 
::sysinit:/bin/sh)
sh: /lib/ld.so.1
< help page of ld.so.1>
sh: /lib/ld.so.1 --verify /bin/xxx (or just any dynamic linked library)
<here the system has crahed>

or
sh: /bin/xxx
<here the system has crashed>

I have tried to step through the dynamic linking, but did not succeed 
til after the creation of a thread.
With a dynamic linked busybox the system stops after a message such as
"freeing xxx kbytes" (I don't know the actual number by head)
When init is then called, which is a part of the busybox which is dyn. 
liked, it crashes.


Greetings,
   Theo

  reply	other threads:[~2005-05-27  5:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-26 21:04 Dynamic libraries do not work Theo Gjaltema
2005-05-26 22:30 ` Grant Likely
2005-05-27  5:36   ` Theo Gjaltema [this message]
2005-05-27  6:53 ` Jaap-Jan Boor
2005-05-27 11:58   ` Theo Gjaltema
2005-05-28  0:50     ` Grant Likely
2005-05-31 20:29   ` Theo Gjaltema

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=4296B1D2.5090409@chello.nl \
    --to=gjalt007@chello.nl \
    --cc=linuxppc-embedded@ozlabs.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.