Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: Jim Blandy <jimb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFC: support debug info in separate files
Date: Tue, 10 Dec 2002 11:39:00 -0000	[thread overview]
Message-ID: <3DF64288.9060706@redhat.com> (raw)
In-Reply-To: <15862.3912.243064.423628@localhost.redhat.com>

> Andrew Cagney writes:
>  > Hmm, to wear fernando's hat :-)  Is there a new test that demonstrates 
>  > this feature?
> 
> You need the special strip program. One could think of avoiding
> running strip by storing the blah.debug files in the gdb.base source
> directory, but then the executable built at the time you run the tests
> wouldn't be stripped as gdb expects it.  One other way would be to
> maybe store the strip program somewhere in the gdb source, but I don't
> think this elfutils/strip is FSF.

Do you have the specifics of the `strip' command and its behavior?  I'll 
suggest it to binutils.  Hopefully (assuming the feature is as useful as 
it sounds) it will soon be added.

To expand on the test.  What I was thinking of was something to check 
that the prefix command worked.

> I know that Jim was able to run the testsuite but I think he relied on
> having the proper strip installed on the system.

Ah!

Andrew



  reply	other threads:[~2002-12-10 19:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-25 20:27 Jim Blandy
2002-11-25 22:34 ` Eli Zaretskii
2002-12-09 19:55   ` Jim Blandy
2002-12-10 12:19     ` Eli Zaretskii
2002-12-09 22:13 ` Elena Zannoni
2002-12-10  8:13   ` Andrew Cagney
2002-12-10  9:14     ` Elena Zannoni
2002-12-10 11:39       ` Andrew Cagney [this message]
2002-12-10 12:43   ` Eli Zaretskii
2002-12-14 16:48   ` Jim Blandy
2002-12-23  1:25 ` Jim Blandy
2002-12-23  1:58 ` [repost] " Jim Blandy
2002-12-23  6:59   ` Eli Zaretskii
2003-01-23 23:04   ` Jim Blandy

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=3DF64288.9060706@redhat.com \
    --to=ac131313@redhat.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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