I didn't want to give this lame answer yesterday, since "zero reply" seems to matter so much in this forum and I think there is a better way, but don't know it. But since no one gave the better way yet, this way works for me:
In another shell, find out the pid of the process you are debugging. Then (in that other shell) do
Code:
less /proc/PID/maps
replacing PID with the actual pid.
Finally, look at the hex address that gdb gave you for that function and scroll down the output from /proc/PID/maps until you find the range that includes that address.
I need to do this fairly often when debugging, so if some expert posts the better way, that will help me as well.