.text, text.hot and text.unlikeley

.text, text.hot and text.unlikeley

[Madhan Sadasivam]

Hello,

Valgrind, the memory error checker does not expect
text.hot and text.unlikeley sections in binaries.

Though everything runs fine, the symbols in these files
are not remembered by Valgrind and hence error
stack traces do not have function names for objects
in these two sections.

The ideal solution is to make Valgrind take care of it.
A quicker way is to merge the 3 text sections as one.
i.e merge text.hot and text.unlikeley into one big ".text"

Is this a sensible thing to do.
Is it possible to do this with any of the binutils tools.

Thanks,
Madhan.

Re: .text, text.hot and text.unlikeley

[Ian Lance Taylor]

Madhan Sadasivam <madhansivam@gmail.com> writes:

> Valgrind, the memory error checker does not expect
> text.hot and text.unlikeley sections in binaries.
>
> Though everything runs fine, the symbols in these files
> are not remembered by Valgrind and hence error
> stack traces do not have function names for objects
> in these two sections.
>
> The ideal solution is to make Valgrind take care of it.
> A quicker way is to merge the 3 text sections as one.
> i.e merge text.hot and text.unlikeley into one big ".text"
>
> Is this a sensible thing to do.
> Is it possible to do this with any of the binutils tools.

You can modify the linker script (printed by ld --verbose) to put
.text.hot* and .text.unlikely* into the .text section.  For more details
see the GNU linker documentation.  Note that the GNU linker is not part
of gcc, it is part of the GNU binutils, a separate project.

Ian

Re: .text, text.hot and text.unlikeley

[Madhan Sadasivam]

Ian,

Thanks for the help. It has certainly worked.

There is also a new .data1 section.
Is this related to text.hot or text.unlikely by any chance.

Thanks,
Madhan.

On Fri, Aug 28, 2009 at 7:46 PM, Ian Lance Taylor<iant@google.com> wrote:
> Madhan Sadasivam <madhansivam@gmail.com> writes:
>
>> Valgrind, the memory error checker does not expect
>> text.hot and text.unlikeley sections in binaries.
>>
>> Though everything runs fine, the symbols in these files
>> are not remembered by Valgrind and hence error
>> stack traces do not have function names for objects
>> in these two sections.
>>
>> The ideal solution is to make Valgrind take care of it.
>> A quicker way is to merge the 3 text sections as one.
>> i.e merge text.hot and text.unlikeley into one big ".text"
>>
>> Is this a sensible thing to do.
>> Is it possible to do this with any of the binutils tools.
>
> You can modify the linker script (printed by ld --verbose) to put
> .text.hot* and .text.unlikely* into the .text section.  For more details
> see the GNU linker documentation.  Note that the GNU linker is not part
> of gcc, it is part of the GNU binutils, a separate project.
>
> Ian
>

Re: .text, text.hot and text.unlikeley

[Ian Lance Taylor]

Madhan Sadasivam <madhansivam@gmail.com> writes:

> There is also a new .data1 section.
> Is this related to text.hot or text.unlikely by any chance.

Not to my knowledge.  I don't know where that is coming from.

Ian