This is the mail archive of the
mailing list for the glibc project.
Re: Regarding "Inconsistency detected by ld.so" 32 Bit Elf
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Karthikeyan Shanmugam <karthikeyan24s at hotmail dot com>
- Cc: "Carlos O'Donell" <carlos at systemhalted dot org>, "libc-help at sourceware dot org" <libc-help at sourceware dot org>
- Date: Tue, 07 May 2013 16:29:38 -0400
- Subject: Re: Regarding "Inconsistency detected by ld.so" 32 Bit Elf
- References: <BLU166-W4365C811BA9EAD5EFFDFDACFB90 at phx dot gbl>,<CAE2sS1jvd97vkPVm+mG=7BBfXX6yYE7POaR75kufrETo40wZkw at mail dot gmail dot com>,<BLU166-W16249AA58CE03F785B384DCFBA0 at phx dot gbl> <BLU166-W3756E8E882E23498AF7DF8CFBA0 at phx dot gbl>
On 05/07/2013 04:14 PM, Karthikeyan Shanmugam wrote:
> The prelink tool and method is working fine, but the required linking
> libraries can change during the product life cycle (explained detail
> in below).
So you're trying, for reasons you can't or won't explain, to have a hole
in the application memory space that you want to reserve for doing something.
You should run `ld --verbose` and use that linker script as a starting point
for *anything* that you do.
You're problem is too complex to talk about in generic, you need to put
together a reduced test case that shows exactly what you're trying to do
and exactly what fails.
Please note that a reduced test case is ONE source file, ONE linker script,
maybe ONE more source file to build a library with, and some instructions.
It has to be simple enough for others on the list to try out and help you with.
It would also be good if that test case works on x86-64 so others can help you.