Small follow up to lock address description: now that we describe
lock address, we can print something even if the lock observation
has no stacktrace.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14190 a5019735-40e9-0310-863c-91ae7b9d1cf9
Add LIKELY as suggested by Philippe.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14191 a5019735-40e9-0310-863c-91ae7b9d1cf9
Have m_addrinfo.c giving more details about an address in a text segment
(using a fake 'one address' stack trace).

This a.o. can be used with the gdbsrv 'monitor v.info location 0x.....'
to compare gdb and valgrind address to source mapping.

Any tool that use pub_tool_addrinfo.h will also better descrive
text addresses.

No impact on tests, as there is no test testing 'segment' address
description :(



git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14192 a5019735-40e9-0310-863c-91ae7b9d1cf9