De-hard code the range in RAM we search for API signature, which might not be
uniform accross architectures and board configurations. Instead use current
global_data pointer as a hint to narrow down the range the [malloc'ed] signature
could reside.
Signed-off-by: Rafal Czubak [EMAIL PROTECTED]
In message [EMAIL PROTECTED] you wrote:
De-hard code the range in RAM we search for API signature, which might not be
uniform accross architectures and board configurations. Instead use current
global_data pointer as a hint to narrow down the range the [malloc'ed]
signature
could reside.
In message [EMAIL PROTECTED] you wrote:
The idea was to discover the proximity of where to look for the API signature
in run-time and only search within some range around it. This way we'd drop
static definitions of the search range.
I think this is pretty unreliable.
The assumption was
