This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Problem in porting GLIBC...
- From: Ian Lance Taylor <ian at airs dot com>
- To: vivek at conjoinsys dot com
- Cc: gcc at gcc dot gnu dot org, "bug-glibc at gnu dot org" <bug-glibc at gnu dot org>
- Date: 16 Feb 2005 20:08:41 -0500
- Subject: Re: Problem in porting GLIBC...
- References: <4139.202.9.146.122.1108556561.squirrel@202.9.146.122>
vivek@conjoinsys.com writes:
> At this stage we are trying to get the 'ld-2.2.5.so' working. We are
> facing problems in this. We are trying to run this on again on our own
> Linux kernel for ABACUS processor. The GOT & PLT generated through the GCC
> for ld-2.2.5.so is causing the problems.
>
> At this moment we are into the main of the user test case. We have jumped
> on the User Entry through the LD.so
>
> There must be some problem in the relocation and now we are unable to
> trace the flow as we are not having the debugger and we use to have print
> statememts to debug the LD. Now it is not possible to use the print
> statements also.
>
> Could you please give us some hint about how to proceed further.
You are in the black magic area. If you have a simulator, you can use
that. Otherwise, since you presumably have a working kernel, you can
usually hack print statements by using inline assembler to do a direct
invocation of the write system call. If that doesn't work, the next
step is probably hand simulation of the instructions in the suspect
code.
Ian