Dynamic libraries do not work

Dynamic libraries do not work

[Theo Gjaltema]

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.

Greetings,
    Theo.

Re: Dynamic libraries do not work

[Grant Likely]

On 5/26/05, Theo Gjaltema <gjalt007@chello.nl> wrote:
> Hello,
>=20
> 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.
>=20
More data please;  Make sure you attach actual output when asking for help.

Re: Dynamic libraries do not work

[Theo Gjaltema]

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

Re: Dynamic libraries do not work

[Jaap-Jan Boor]

Theo,

What type of processor are you using? 8xx?
Did you build a tool-chain yourself and are
you perhaps using floating point?

Jaap-Jan

On 26-mei-2005, at 23:04, Theo Gjaltema 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.
>
> Greetings,
>    Theo.
>
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>

____
J.G.J. Boor                       Anton Philipsweg 1
Software Engineer                 1223 KZ Hilversum
AimSys bv                         tel. +31 35 689 1941
Postbus 2194, 1200 CD Hilversum   jjboor at aimsys dot nl

Re: Dynamic libraries do not work

[Theo Gjaltema]

Toolchain used:   ELDK 2.0
target processor: mpc862
RAM:                64 Mbyte
Kernel:               2.4.20, extended with ATM/UTOPIA
init:                  /sbin/init -> /bin/busybox


(using a static linked busybox: activating a sh (=busybox)  
::sysinit:/bin/sh)
sh: /lib/ld.so.1          (note: /lib/ld.so.1 is a link to 
/lib/ld.so.2.5.5, part of the ELDK 2.0 )
< help page of ld.so.1>
sh: /lib/ld.so.1 --verify /bin/xxx (or just any dynamic linked executable)
<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
Jaap-Jan Boor schreef:

> Theo,
>
> What type of processor are you using? 8xx?
> Did you build a tool-chain yourself and are
> you perhaps using floating point?
>
> Jaap-Jan
>
> On 26-mei-2005, at 23:04, Theo Gjaltema 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.
>>
>> Greetings,
>>    Theo.
>>
>>
>> _______________________________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded@ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>
>
> ____
> J.G.J. Boor                       Anton Philipsweg 1
> Software Engineer                 1223 KZ Hilversum
> AimSys bv                         tel. +31 35 689 1941
> Postbus 2194, 1200 CD Hilversum   jjboor at aimsys dot nl
>
>
>

Re: Dynamic libraries do not work

[Grant Likely]

On 5/27/05, Theo Gjaltema <gjalt007@chello.nl> wrote:
>=20
>=20
> Toolchain used:   ELDK 2.0
> target processor: mpc862
> RAM:                64 Mbyte
> Kernel:               2.4.20, extended with ATM/UTOPIA
> init:                  /sbin/init -> /bin/busybox
>=20
>=20
> (using a static linked busybox: activating a sh (=3Dbusybox)
> ::sysinit:/bin/sh)
> sh: /lib/ld.so.1          (note: /lib/ld.so.1 is a link to
> /lib/ld.so.2.5.5, part of the ELDK 2.0 )
> < help page of ld.so.1>
> sh: /lib/ld.so.1 --verify /bin/xxx (or just any dynamic linked executable=
)
> <here the system has crahed>
>=20
> or
> sh: /bin/xxx
> <here the system has crashed>
>=20
> 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.
>=20
It's really hard to give any advice with the limited data.
Do you get a kernel panic?  Has the kernel crashed or has it become
unresponsive.  Making a large number of assumptions, it sounds like
you've got a kernel problem, not a dynamic linking problem.  Dynamic
linking is handled 100% in user space.  If init crashes (or is killed)
you should get a kernel panic message.  The fact that you get nothing
says to me that dynamic linking is simply exposing a kernel bug.

A good place to start is to make sure all of memory is working.  Try a
simple test; allocate memory in an infinite loop and see where it
breaks.

Cheers,
g.

Re: Dynamic libraries do not work

[Theo Gjaltema]

I 've found the problem, the ramdisk used contained executables as well 
as dyn. libs from the mpc8260 instead of the mpc862.
I don't know why the whole system came to a halt without any message but 
replacing the dyn. libs and executables with the correct ones solved the 
problem of crashing.

Many thanks for your responses,
   Theo.



Jaap-Jan Boor schreef:

> Theo,
>
> What type of processor are you using? 8xx?
> Did you build a tool-chain yourself and are
> you perhaps using floating point?
>
> Jaap-Jan
>
> On 26-mei-2005, at 23:04, Theo Gjaltema 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.
>>
>> Greetings,
>>    Theo.
>>
>>
>> _______________________________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded@ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>
>
> ____
> J.G.J. Boor                       Anton Philipsweg 1
> Software Engineer                 1223 KZ Hilversum
> AimSys bv                         tel. +31 35 689 1941
> Postbus 2194, 1200 CD Hilversum   jjboor at aimsys dot nl
>
>
>