public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Luis Machado (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: gdb-patches@sourceware.org
Subject: [review] [Obvious] Remove stale FIXME comment
Date: Wed, 27 Nov 2019 20:27:00 -0000	[thread overview]
Message-ID: <gerrit.1574886458000.I2436ca4ae4a6741012cafe8123325f738b692c9c@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1574886458000.I2436ca4ae4a6741012cafe8123325f738b692c9c@gnutoolchain-gerrit.osci.io>

Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/732
......................................................................

[Obvious] Remove stale FIXME comment

While debugging something, i noticed this odd FIXME comment. It seems stale
and therefore here's a patch removing it.

gdb/ChangeLog:

2019-11-27  Luis Machado  <luis.machado@linaro.org>

	* infrun.c (follow_fork_inferior): Remove outdated FIXME comment.

Change-Id: I2436ca4ae4a6741012cafe8123325f738b692c9c
---
M gdb/infrun.c
1 file changed, 0 insertions(+), 1 deletion(-)



diff --git a/gdb/infrun.c b/gdb/infrun.c
index 3718674..6a346d6 100644
--- a/gdb/infrun.c
+++ b/gdb/infrun.c
@@ -432,7 +432,6 @@
 Can not resume the parent process over vfork in the foreground while\n\
 holding the child stopped.  Try \"set detach-on-fork\" or \
 \"set schedule-multiple\".\n"));
-      /* FIXME output string > 80 columns.  */
       return 1;
     }
 

-- 
Gerrit-Project: binutils-gdb
Gerrit-Branch: master
Gerrit-Change-Id: I2436ca4ae4a6741012cafe8123325f738b692c9c
Gerrit-Change-Number: 732
Gerrit-PatchSet: 1
Gerrit-Owner: Luis Machado <luis.machado@linaro.org>
Gerrit-MessageType: newchange

       reply	other threads:[~2019-11-27 20:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27 20:27 Luis Machado (Code Review) [this message]
2019-12-02 14:24 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-12-02 14:24 ` Sourceware to Gerrit sync (Code Review)

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=gerrit.1574886458000.I2436ca4ae4a6741012cafe8123325f738b692c9c@gnutoolchain-gerrit.osci.io \
    --to=gerrit@gnutoolchain-gerrit.osci.io \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).