objdump -S doesn't include source for all modules

Seems to me, that newer binutils even more broken than older binutils. I tested sparc-rtems-objdump (version 2.18) vs. sparc-elf-objdump (version 2.16.1).

sparc-elf-objdump -dS -l (version 2.16.1)

------------------------------------------ Same behavior for dos2unix & unix2dos sources:

- All object (module) disassembler files are correct.

- The executable (application) disassembly shows the C-source of some modules, for other modules it doesn't

- AFAIS same modules show/don't show for dos2unix & unix2dos C-sources.

- AFAIS (as far as I see) line numbers (objdump -l) for all modules are correct.

sparc-rtems-objdump -dS -l (version 2.18)

------------------------------------------- unix2dos sources:

- All object disassembler files show correct filenames & line numbers, but *no sources*

- The executable disassembly also shows correct filenames & line numbers, but *no C-sources*

dos2unix sources: (!!!)

- All object disassembler files show correct line information, and

- AFAIS the executable disassembly shows correct filenames and line numbers.

- For some modules the C-source is not shown

- For other modules the C-source is shown correctly

- For other modules the C-source is shown from *an invalid file, same line number* (!!!) (see below: main() is defined in main.c:419, not in memory)

Disassembly of executable/memory module:

---------------------------------------- ... D:\Projekt\Bela\prog\pbs-1/memory.c:419 int main(void) {

Rolf

I'd post this to the binutils newsgroup: you are more likely to get a result there.

Andrew

I've never found objdump to be able to reliably and usefully intersperse source code into a dissassembly listing. You're far better off creating the mixed-language listing at compile time by using a makefile rule something like this:

%.o: %.c $(GCC) $(CFLAGS) $(INCLUDES) -c $< -o $@ -Wa,-ahldn=$(@F).l

The "-Wa..." bit at the end is what creates the mixed-mode listing.

Thanks a lot, I wasn't aware about -Wa.

But getting a disassembly of a single C-module also seems to work fine with objdump. What I need is a disassembly of the complete (linked) target image. And this seems to be impossible with objdump -dS ...

Grant Edwards wrote, >

It varies. It works OK for some targets, for some source files, and for some combinations of compiler flags.

In my experience, you are correct -- objdump isn't capable of that. I've never had a need for a global listing like that, so I'm afraid I can't be of much help.