Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Tom Tromey <tromey@redhat.com>,
	        gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFA] Fix too many "no debugging symbols found" warnings.
Date: Tue, 30 Jun 2009 22:20:00 -0000	[thread overview]
Message-ID: <e394668d0906301520s29f06d4bh8ea9593d15383682@mail.gmail.com> (raw)
In-Reply-To: <200906302256.40646.pedro@codesourcery.com>

On Tue, Jun 30, 2009 at 2:56 PM, Pedro Alves<pedro@codesourcery.com> wrote:
> On Tuesday 30 June 2009 22:49:25, Doug Evans wrote:
>> On Mon, Jun 22, 2009 at 12:35 PM, Pedro Alves<pedro@codesourcery.com> wrote:
>> > On Monday 22 June 2009 18:52:40, Tom Tromey wrote:
>> > I like gdb's output with
>> > Doug's suggestion.
>>
>> So we have two yeas and zero nays.
>
> To be clear, that referred to the making "gdb program" print
> something (passing !batch as is_atty flag in main.c).  I haven't
> really looked at the patch or the rest of the suggestion
> carefully.  :-)

Righto.  I took Tom's email as approval of the patch, his only concern
was to wait to let people comment on the output.

But if you want the patch to wait for more review, ok.


  reply	other threads:[~2009-06-30 22:20 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-23 23:24 Doug Evans
2009-05-25  3:20 ` Eli Zaretskii
2009-05-25 16:07   ` Doug Evans
2009-06-04 20:34     ` Tom Tromey
2009-06-04 21:20       ` Pedro Alves
2009-06-05 18:19         ` Tom Tromey
2009-06-05 18:49           ` Pedro Alves
2009-06-05 22:18             ` Tom Tromey
2009-06-19  0:48               ` Doug Evans
2009-06-22 17:54                 ` Tom Tromey
2009-06-22 19:35                   ` Pedro Alves
2009-06-30 21:49                     ` Doug Evans
2009-06-30 21:55                       ` Pedro Alves
2009-06-30 22:20                         ` Doug Evans [this message]
2009-07-01  2:29                           ` Tom Tromey
2009-07-01  3:13                       ` Eli Zaretskii
2009-07-01  3:47                         ` Doug Evans
2009-07-01 17:48                           ` Eli Zaretskii
2009-07-01 17:53                             ` Doug Evans
2009-07-01 18:01                               ` Pedro Alves
2009-07-01 19:55                                 ` Doug Evans
2009-07-02 13:26                                   ` Pedro Alves
2009-07-02 20:08                                     ` Doug Evans
2009-07-02 22:43                                       ` Pedro Alves
2009-07-11  4:22                                         ` Doug Evans
2009-07-20 13:21                                           ` Pedro Alves
2009-07-23 18:57                                             ` Doug Evans
2009-07-27 17:15                                               ` Tom Tromey
2009-08-24 22:02                                                 ` Doug Evans
2009-08-25  3:47                                                   ` Eli Zaretskii
2009-08-27 19:11                                                   ` Tom Tromey
2009-08-27 23:39                                                     ` Doug Evans

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=e394668d0906301520s29f06d4bh8ea9593d15383682@mail.gmail.com \
    --to=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=tromey@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