Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: ezannoni@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFC/WIP] unit test for separate debug info
Date: Tue, 11 Nov 2003 16:26:00 -0000	[thread overview]
Message-ID: <16305.3508.239806.128368@localhost.redhat.com> (raw)
In-Reply-To: <200311080128.hA81SnLk029187@duracef.shout.net>

Michael Elizabeth Chastain writes:
 > I gave it some proof-reading but did not try running it yet.
 > 
 > The idea looks okay to me.
 > 
 > For documentation, it would help to just have a list of files at the top:
 > 
 >   gdb.base/break            original executable
 >   gdb.base/break.stripped   stripped executable
 >   gdb.base/break.sym        debug symbols
 >   gdb.base/break.debuglink  output of --add-gnu-debuglink
 > 
 > (Hmmm, my list of files does not have any .debug directory!)
 > 
 > Human beings are good at reading examples and extrapolating
 > from them, and not as good at handling explicit meta-variables.
 > 

Indeed. The comments must be misleading, because the names of the
files you listed above are not the correct ones. So I'll add such a comment.
The files are

gdb.base/break-->original executable
gdb.base/break.stripped-->stripped exec
gdb.base/.debug/break.debug-->debuginfo only
gdb.base/break-->original exec minus debug symbols plus link to the .debug file



 > I would really like break.debuglink to be a separate file from the
 > original file.  If somebody is debugging this process, it's much better
 > to have each file be unique.

At first thought I'd say no, because that's not what you'll encounter
in practice. You would be testing something different. Close but
different. I.e. original executable name == name of final executable.
Indeed if you get a RedHat distro, you get all stripped binaries, but
their names are the usual ones.  However, on second thought it may work
anyway. I'll play with it.

 > 
 > In gdb_gnu_strip_debug, what are the final values of "strip_to_file_program"
 > and "objcopy_program" going to be?  I am hoping that they will just be
 > 
 >   set strip_to_file_program strip
 >   set objcopy_program       objcopy
 > 

yes. I had to tweak them in order to pick up the copies that had the
features, the ones installed on the systems were too old. Note the
failure mode as well. It produces an unsupported. For the RedHat case,
it would pick up eu-strip (but in reality the whole procedure is
different anyway).

 > Well, actually that works only for natives, crosses need more work.
 > 

yes. I am not planning on doing that right now. I guess I should make
the test work only for natives.

 > I would say, leave the elfutils case out for now.
 > 

yep.

 > Michael C


  reply	other threads:[~2003-11-11 16:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-08  1:28 Michael Elizabeth Chastain
2003-11-11 16:26 ` Elena Zannoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-11 21:19 Michael Elizabeth Chastain
2003-11-11 21:22 ` Daniel Jacobowitz
2003-11-12 14:44 ` Elena Zannoni
2003-11-07 20:21 Michael Elizabeth Chastain
2003-11-07 20:03 Elena Zannoni
2003-11-07 20:39 ` Kevin Buettner

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=16305.3508.239806.128368@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    /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