This is the mail archive of the
mailing list for the binutils project.
RE: Listing source files with objdump
- From: Bruce Dawson <bruced at valvesoftware dot com>
- To: 'nick clifton' <nickc at redhat dot com>, "'binutils at sourceware dot org'" <binutils at sourceware dot org>
- Date: Wed, 5 Jun 2013 19:08:19 +0000
- Subject: RE: Listing source files with objdump
- References: <2AC155A009400B4C8B05D518E4819AEF07205A43 at exchange10 dot valvesoftware dot com> <51AF119C dot 5090605 at redhat dot com>
I'll poke around and see if I can submit a patch. The actual coding is simple enough, but I may decide not to bother submitting just 'cause that always takes a while on a new project.
I do have access to the build system -- this is running on the build machine. The main value it has over the list of source files in the makefile is that it also includes any header files that were brought in, which may contain a significant amount of code.
For each file I then get the Perforce path and version information, which gives us a machine-neutral specifier for all of the files.
From: nick clifton [mailto:email@example.com]
Sent: Wednesday, June 05, 2013 3:23 AM
To: Bruce Dawson; 'firstname.lastname@example.org'
Subject: Re: Listing source files with objdump
> I want to get a list of all of the source files and header files used to create a particular shared object.
Presumably you do not have access to the build system that created the shared object in the first place ?
> Does it seem worthwhile to add a new objdump command line option to > just dump this information? I could see it being useful for others.
> Perhaps -WS for Source.
Go for it. :-)