Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: Elena Zannoni <ezannoni@redhat.com>,
	Eli Zaretskii <eliz@elta.co.il>,
	gdb-patches@sources.redhat.com
Subject: Re: RFA: document binutils support for separate debug info
Date: Fri, 27 Jun 2003 12:28:00 -0000	[thread overview]
Message-ID: <3EFC386A.6070807@redhat.com> (raw)
In-Reply-To: <vt2fzlwdnwv.fsf@zenia.home>

> Elena Zannoni <ezannoni@redhat.com> writes:
> 
> 
>> Eli Zaretskii writes:
>>  > > From: Jim Blandy <jimb@redhat.com>
>>  > > Date: 25 Jun 2003 12:35:00 -0500
>>  > > 
>>  > > 2003-06-25  Jim Blandy  <jimb@redhat.com>
>>  > > 
>>  > > 	* gdb.texinfo (Separate Debug Files): Update documentation to
>>  > > 	describe GNU Binutils' support for separate debug info files.
>>  > 
>>  > Approved.  Thanks.
>> 
>> 
>> Wait a second. I am fixing gdb bugs ATM with that code.
>> I think let's hold the doco until it works completely.
> 
> 
> Yes, Nick just told me that things are in flux, too.  I tried things
> out and what I tried worked (I didn't fake the example!) but I'm happy
> to wait and see how things settle out.
> 
> Do you have the Dejagnu magic to run the entire test suite with
> separate debug info?  I keep wanting to integrate it into
> testsuite/lib/gdb.exp so one can get it just by adding magic to one's
> target_list, but I don't get around to it.

There really needs to be a unit test for this feature.  That way people 
will know it works, even when their system isn't set up to use it.

Andrew



  reply	other threads:[~2003-06-27 12:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-25 18:31 Jim Blandy
2003-06-26  5:06 ` Eli Zaretskii
2003-06-26 14:08   ` Elena Zannoni
2003-06-27  6:40     ` Jim Blandy
2003-06-27 12:28       ` Andrew Cagney [this message]
2003-06-27 17:30       ` Eli Zaretskii

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=3EFC386A.6070807@redhat.com \
    --to=ac131313@redhat.com \
    --cc=eliz@elta.co.il \
    --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