twgray writes:

> How do I get g++
> to generate an object/function relative address listing?

You don't: g++ produces *relocatable* objects, which linker then
links into a final executable. Only at link stage are function
addresses assigned.

You can use 'nm a.out' to find out what these assignments are,
or use '-Wl,--print-map' (or '-Wl,-Map,foo.map') at link time to
get a link map.

Cheers,
--
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.

On Feb 16, 9:59*pm, Paul Pluzhnikov wrote:
> twgray writes:
> > How do I get g++
> > to generate an object/function relative address listing?
>
> You don't: g++ produces *relocatable* objects, which linker then
> links into a final executable. Only at link stage are function
> addresses assigned.
>
> You can use 'nm a.out' to find out what these assignments are,
> or use '-Wl,--print-map' (or '-Wl,-Map,foo.map') at link time to
> get a link map.
>
> Cheers,
> --
> In order to understand recursion you must first understand recursion.
> Remove /-nsp/ for email.

Thanks. Exactly what I needed.