All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: GRUB2: Keeping debug symbols in an image
Date: Tue, 21 Feb 2012 13:50:45 +0100	[thread overview]
Message-ID: <4F439325.4030600@gmail.com> (raw)
In-Reply-To: <CAGi1eXWPtaJXq0j0KZAZNQvH-RxNXnkq5ia-oQF1-eSGvBdi_Q@mail.gmail.com>

On 21.02.2012 00:16, Adrian Burns wrote:
> Hi, i had sent this out to help-grub@gnu.org but perhaps its best sent to devel
>
> Im looking for GRUB2's grub-mkimage to produce an efi file for target
> execution along with a matching elf file that has all the debug
> symbols included so that i can use a debugger to step through the
> GRUB2 code. So far i see that strip is used in
> grub/grub-core/genmod.sh.in to strip debug sections from the *.o files
> as the build generates the *.mod file (i used readelf to verify this
> after commenting out the strip command below) Then in grub-mkimage.c,
> the generate_image() function appears to make no attempt to preserve
> symbols. Is there a way to tell the build system to leave modules and
> images with full symbol table and debugging information?
We don't put any debug symbols to the result image. Use *.image and 
*.module. They are exact counterpart or *.img and *.mod other than being 
ELF even if *.img isn't and not having module identication sections.
> for the image....has anyone modified grub-mkimage.c to retain debug
> symbols in generated image?
>
> thanks,
> Adrian
>
>

-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



      reply	other threads:[~2012-02-21 12:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20 23:16 GRUB2: Keeping debug symbols in an image Adrian Burns
2012-02-21 12:50 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]

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=4F439325.4030600@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.