Re: Inequivalent aliases when stracing tst-cputimer1.
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
On 7/3/2011 10:39 PM, Carlos O'Donell wrote:
James, Dave, While running some glibc tests on 2.6.39-rc3a+ I noticed the following: ~~~ ... [ 7649.424000] INEQUIVALENT ALIASES 0x13000 and 0x14000 in file tst-cputimer1 [ 7649.568000] INEQUIVALENT ALIASES 0x13000 and 0x14000 in file tst-cputimer1 [ 7649.720000] INEQUIVALENT ALIASES 0x13000 and 0x14000 in file tst-cputimer1 ... ~~~ This is a binutils head, building glibc head, with gcc 4.4.4. This *only* happens when I strace the application. While the application is being strace'd it continually dumps the same message about inequivalent aliases. Any idea what's going on here? How can I fix it? :-)
You need to update binutils to get new linker (actually, it's the default linker script that's changed).
The new linker script starts the data section on a page boundary.It's not GCC version dependent. However, newer GCC versions have improved delay slot handling.
It's caused by overlapping mappings of text and data which you can see by dumping the maps file for the process. I think I may have back ported the fix. If you build binutils head, you will have to
configure with --disable-initfini-array to build glibc.I don't know all the circumstances under which the message appears. It always occurs on a core dump. It occurs when a page needs to be flushed and there are two or more inequivalent aliases
to the page. It's probably harmless on A500. It affects PA8800/PA8900. Dave -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html