Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] "$ gdb PROGRAM" vs "(gdb) file PROGRAM" difference; warn on failure to remove breakpoint.
Date: Mon, 16 Jun 2014 14:44:00 -0000	[thread overview]
Message-ID: <539F02C6.6000504@redhat.com> (raw)
In-Reply-To: <1402323778-27849-1-git-send-email-palves@redhat.com>

On 06/09/2014 03:22 PM, Pedro Alves wrote:

> I say "restores" because this was GDB's behavior in 7.7 and earlier.
> 
> And, likewise, "file" with no arguments only started turning
> breakpoints set in the main executable to "<pending>" with the
> remote-symbol-file patch (63644780).  The old behavior is now
> restored, and we break-unload-file.exp test now exercizes both "gdb;
> file PROGRAM" and "gdb PROGRAM".

I've now pushed this to both mainline and the 7.8 branch.

-- 
Pedro Alves


      parent reply	other threads:[~2014-06-16 14:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09 14:23 Pedro Alves
2014-06-11 19:01 ` Tom Tromey
2014-06-12  3:49 ` Yao Qi
2014-06-12 12:07   ` Pedro Alves
2014-06-12 13:23     ` Yao Qi
2014-06-12 13:25       ` Pedro Alves
2014-06-16 14:44 ` Pedro Alves [this message]

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=539F02C6.6000504@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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