Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: ezannoni@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFC/WIP] unit test for separate debug info
Date: Sat, 08 Nov 2003 01:28:00 -0000	[thread overview]
Message-ID: <200311080128.hA81SnLk029187@duracef.shout.net> (raw)

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.

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.

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

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

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

Michael C


             reply	other threads:[~2003-11-08  1:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-08  1:28 Michael Elizabeth Chastain [this message]
2003-11-11 16:26 ` Elena Zannoni
  -- 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=200311080128.hA81SnLk029187@duracef.shout.net \
    --to=mec@shout.net \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    /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