Von: Grant Edwards
Gesendet am: 02 Jul 2010 16:27:35
It has, however, some serious drawbacks.
As in it doesn't work? :)
Well this IS a drawback, isn't it? :)
Generating source listings from a linked program using objdump has
never worked for any target architecture I've tried. IMO,
Von: N. Coesel
Gesendet am: 01 Jul 2010 14:19:57
I too use objdump to generate a complete project listing from the elf
file.
It has, however, some serious drawbacks. Not only that jumps and calls
are not printed with their symbolic name, also the source code in the
listing
is sometimes
On 2010-07-02, JMGross msp...@grossibaer.de wrote:
Von: N. Coesel
Gesendet am: 01 Jul 2010 14:19:57
I too use objdump to generate a complete project listing from the elf
file.
I've never seen that work except for extremely trivial programs.
It has, however, some serious drawbacks.
As in
I too use objdump to generate a complete project listing from the elf file.
It has, however, some serious drawbacks. Not only that jumps and calls
are not printed with their symbolic name, also the source code in the listing
is sometimes (often) from a completely different file or from different
I noticed the missing C source in mspgcc4 too a while ago. There is a
difference between mspgcc3 and mspgcc4 in this area. But it could also
be the underlying binutils which cause this behaviour.
Just tried to compile an ordinary X86 program using GCC 4.4.3 on Ubuntu
with these options:
CFLAGS
- Original Message -
From: JMGross msp...@grossibaer.de
To: MSPGCC mailing list, mspgcc-users@lists.sourceforge.net
Sent: Thursday, July 01, 2010 12:42 PM
Subject: Re: [Mspgcc-users] Creating .lst files with C code
I too use objdump to generate a complete project listing from
On Thu, 1 Jul 2010 14:19:57 +0200
N. Coesel n...@nctdev.nl wrote:
AFAIK this is the result of compiling with optimisation on. If you want a
proper
list file with source code mixed in, you should compile without optimisation
(-O0) and with full
debugging enabled (IIRC -g3). At least thats
Excellent; thank you. With this help I've determined that the msp430
patches to gcc don't enable the check for dwarf2 support on that
architecture; as a result the compiler won't generate the line information
required for integrated listings. This is probably why another user has
complained that
On 2010-06-30, Diane Gagne drose.ga...@gmail.com wrote:
I am in the process of moving from mspgcc 3.2.3 to mspgcc4, but I am
having trouble with the creation of the .lst files. When my source
is compiled with the 3.2.3 the list files have the C code printed in
them along with the assembly.