__builtin_return_address returns null for index >0?

Question

I want to get the return address of the caller function. I'm using __builtin_return_address() funtion, but if I give index value greater than 0 it is returning NULL.

Please help me with this or tell me any other function to get the same.

"This function should only be used with a nonzero argument for debugging purposes." If you need a stack trace, there are other functions available. — Drew McGowen, Nov 12 '14 at 13:28
@Deduplicator I need to store the return address of the caller function. — Vishesh Bhalla, Nov 13 '14 at 04:24
Please explain what motivates your question. Why do you need the return address of the caller function? What will you do with it? Show more code please, so edit your question. — Basile Starynkevitch, Nov 13 '14 at 06:05

score 5 · Accepted Answer · edited May 23 '17 at 10:29

5

See this answer to a related question.

__builtin_return_address is GCC and processor specific (also available in some versions of Clang on some processors with some -lack of- optimizations), and documented as

On some machines it may be impossible to determine the return address of any function other than the current one

The compiler might optimize a function (e.g. when it is compiled with -fomit-frame-pointer, or for tail-calls, or by function inlining) without the relevant information.

So probably you are getting NULL because the information is not available!

edited May 23 '17 at 10:29

Community

1
1

answered Nov 12 '14 at 13:27

Basile Starynkevitch

223,805
18
296
547

Thanks!! Can you tell me any other function which gives the return address of the function which is not processor specific or works on ARMv7. – Vishesh Bhalla Nov 13 '14 at 04:35
Probably, the information is not available. So no way to get something that does not exist. – Basile Starynkevitch Nov 13 '14 at 06:03

score 2 · Answer 2 · answered Sep 07 '15 at 12:49

In addition to compiler optimisation reasons (which IMO is the most likely reason for the issue you're facing), the GCC documentation states quite plainly:

Calling this function with a nonzero argument can have unpredictable effects, including crashing the calling program. As a result, calls that are considered unsafe are diagnosed when the -Wframe-address option is in effect. Such calls should only be made in debugging situations.

As Basile said, since it's a compiler builtin (read: very processor specific and a bad idea to use) the behaviour is exceptionally loosely defined (as it is not required by any standards and does not have to make any guarantees).

Just use backtrace(3), it's POSIX-compliant and doesn't rely on compiler builtins.

__builtin_return_address returns null for index >0?

2 Answers2

Linked