This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: how to source level debug if I cannot see source embedded in elf file

From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
To: loody <miloody at gmail dot com>
Cc: Simon Richter <Simon dot Richter at hogyros dot de>, gdb at sourceware dot org
Date: Mon, 23 Nov 2009 14:46:07 +0000
Subject: Re: how to source level debug if I cannot see source embedded in elf file
References: <3a665c760911220903y352e7062m2acfd5fb27a1b169@mail.gmail.com> <20091122171617.GL18195@honey.hogyros.de> <3a665c760911221602y6ff771bdlbccdd27dc9fc0012@mail.gmail.com>

loody wrote:

> mipsel-unknown-elf-ld -T ./link.xn -o TestCode.elf -Map TestCode.map
> --oformat elf32-littlemips  init.o reset.o atexit.o main.o -static
> -nostdlib -L/media/sdb1/newlib-1.17.0/build/mipsel/lib
> -L/root/bare_metal/x-tools/mipsel-unknown-elf/lib/gcc/mipsel-unknown-elf/4.2.4
>  -lc -lnullmon -lgcc

  Is your linker script discarding the debug info sections?  Look at "objdump
-h" of TestCode.elf and of one of the .o files for comparison; if the .o files
have debug info sections but not the .elf, the problem is probably there.

    cheers,
      DaveK

References:
- how to source level debug if I cannot see source embedded in elf file
  - From: loody
- Re: how to source level debug if I cannot see source embedded in elf file
  - From: Simon Richter
- Re: how to source level debug if I cannot see source embedded in elf file
  - From: loody

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]