On Sun, 7 Apr 2019, Stephen M. Webb wrote:
> On 2019-04-07 11:55 AM, Robert P. J. Day wrote:
> >
> > i'm sure that, once upon a time, using either readelf or objdump, i
> > found a variation with a certain collection of options that displayed
> > no more than each included routine in the final ELF file and the
> > source file it came from. and at the moment, i am completely
> > forgetting how i did it.
>
> A stripped ELF file is not going to have any debug information (eg.
> the source file from which a bunch of binary objects in a particular
> segment was compiled). If you're creating the boot image you might
> need to tweak things so the debug information doesn't get stripped
> out during the build.
>
> The debug information is stored in DWARF tables inside of the ELF
> file. Try playing with the --debug-dunmp and the --dwarf-* options
> to readelf.
except i'm *sure* that i did this once upon a time without tweaking
the compile stage. i'll try to figure out how i did this before,
unless i'm misremembering what i did.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
To unsubscribe send a blank message to linux+unsubscribe [ at ] linux-ottawa [ dot ] org
To get help send a blank message to linux+help [ at ] linux-ottawa [ dot ] org
To visit the archives: https://lists.linux-ottawa.org