Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: maybedoo <maybedoo@gmx.de>
To: gdb@sourceware.org
Subject: Re: Elf debugging
Date: Thu, 04 Jun 2009 13:42:00 -0000	[thread overview]
Message-ID: <23870188.post@talk.nabble.com> (raw)
In-Reply-To: <8ac60eac0906031507v74e98d59q9ed983f498cc4dc4@mail.gmail.com>


Hmm it's strange that i've no debug information in elfboot.c?

Here is the ls from the src directory:

may@debian:~/coreboot/coreboot-v2/src/boot$ ls
Config.lb  elfboot.c  filo.c  hardwaremain.c  selfboot.c


Problem is that I need elfboot.c for a breakpoint.

Thanks for your help Paul with readelf. Didn't know that and how to use it.

Regards,

May


Paul Pluzhnikov-4 wrote:
> 
> On Wed, Jun 3, 2009 at 4:31 AM, maybedoo <maybedoo@gmx.de> wrote:
> 
>> (gdb) break elfboot.c:20
>> No source file named elfboot.c.
> 
> Are you sure this isn't a "pilot error"?
> I see that you have selfboot.c, but no elfboot.c.
> 
> Here are the files which have debug info (and which you shouldn't have
> problems setting breakpoints in):
> 
> $ grep 'DW_AT_name.*\.c' readelf.txt  | sed -e 's/.*: //' -e 's:.*//::'
> 
> src/southbridge/intel/i82371eb/i82371eb_smbus.c
> src/console/uart8250_console.c
> src/southbridge/intel/i82371eb/i82371eb.c
> src/southbridge/intel/i82371eb/i82371eb_usb.c
> src/southbridge/intel/i82371eb/i82371eb_reset.c
> src/southbridge/intel/i82371eb/i82371eb_isa.c
> src/southbridge/intel/i82371eb/i82371eb_ide.c
> src/mainboard/emulation/qemu-x86/mainboard.c
> src/arch/i386/lib/exception.c
> src/devices/root_device.c
> src/lib/uart8250.c
> src/console/printk.c
> src/pc80/mc146818rtc.c
> src/boot/hardwaremain.c
> src/devices/pci_device.c
> src/lib/version.c
> src/devices/cardbus_device.c
> src/pc80/keyboard.c
> src/devices/pciexp_device.c
> src/devices/pci_ops.c
> src/console/console.c
> src/devices/hypertransport.c
> src/devices/device.c
> src/lib/malloc.c
> src/devices/device_util.c
> src/devices/../../util/x86emu/x86.c
> src/pc80/isa-dma.c
> src/lib/memmove.c
> src/lib/memcpy.c
> src/lib/memset.c
> src/console/vtxprintf.c
> static.c
> src/arch/i386/boot/tables.c
> src/boot/selfboot.c
> src/devices/pci_rom.c
> src/arch/i386/boot/coreboot_table.c
> src/devices/pcix_device.c
> src/cpu/emulation/qemu-x86/northbridge.c
> src/mainboard/emulation/qemu-x86/irq_tables.c
> src/devices/../../util/x86emu/x86_interrupts.c
> src/arch/i386/boot/boot.c
> src/lib/delay.c
> src/arch/i386/lib/pci_ops_auto.c
> src/console/vsprintf.c
> src/arch/i386/lib/pci_ops_conf2.c
> src/lib/cbfs.c
> option_table.c
> src/lib/compute_ip_checksum.c
> src/lib/fallback_boot.c
> src/arch/i386/boot/pirq_routing.c
> src/arch/i386/boot/multiboot.c
> src/lib/lzma.c
> src/arch/i386/lib/pci_ops_conf1.c
> 
> Cheers,
> -- 
> Paul Pluzhnikov
> 
> 

-- 
View this message in context: http://www.nabble.com/Elf-debugging-tp23814190p23870188.html
Sent from the Sourceware - gdb list mailing list archive at Nabble.com.


  reply	other threads:[~2009-06-04 13:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01 12:24 maybedoo
2009-06-01 19:37 ` Michael Snyder
2009-06-02 17:15   ` maybedoo
2009-06-02 19:23     ` Paul Pluzhnikov
2009-06-03 11:31       ` maybedoo
2009-06-03 22:07         ` Paul Pluzhnikov
2009-06-04 13:42           ` maybedoo [this message]
2009-06-04 14:12             ` maybedoo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=23870188.post@talk.nabble.com \
    --to=maybedoo@gmx.de \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox