public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@ericsson.com>
To: Brian Vandenberg <phantall@gmail.com>,
	"brobecker@adacore.com"	<brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"ro@cebitec.uni-bielefeld.de" <ro@cebitec.uni-bielefeld.de>
Subject: Re: [PATCH][PR gdb/8527] Interrupt not functional in Eclipse/CDT on Solaris
Date: Fri, 09 Nov 2018 22:08:00 -0000	[thread overview]
Message-ID: <5e65ba26-c0b6-ab77-a682-933f3bcd1827@ericsson.com> (raw)
In-Reply-To: <CAEJ-0i98-Vz3Gw=S1j25q_d_29RKORMwKnsZHNJb0sXmdcyXiA@mail.gmail.com>

On 2018-11-01 5:45 p.m., Brian Vandenberg wrote:
> Greetings,
> 
> Did you run the testsuite before and after the patch, by any chance?
> 
> 
> Nope.  In my work environment I don't have much flexibility on
> getting/installing software.  If I run the test suite I would probably have
> to setup an IllumOS VM at home to run it, but that'd be x86 not SPARC.
> 
> 
> For multiline comments like the above, we do not repeat the '*'
>> at the beginning of each line.
>>        /* PR gdb/8527: Was not correctly interrupting the inferior process
>>           when ^C was pressed in the debug terminal.  */
>> And if I may, reading this sentence, it's a bit hard to understand
>> what the comment is trying to explain. The following might be
>> a little more precise:
>>        /* PR gdb/8527: Call set_sigint_trap to make sure that a ctrl-c
>>           pressed in the debugger terminal gets passed down to the
>>           inferior, thus causing it to be interrupted.  */
> 
> 
> I've no qualms with those changes.  Thanks for your feedback.

Asking because it's ambiguous... do you plan on sending an updated patch?

As for the patch content and its testing, perhaps Rainer can give some feedback.

Simon


  reply	other threads:[~2018-11-09 22:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-07 19:13 Brian Vandenberg
2018-11-01 21:19 ` Joel Brobecker
2018-11-01 21:46   ` Brian Vandenberg
2018-11-09 22:08     ` Simon Marchi [this message]
2018-11-09 22:22       ` Rainer Orth
2018-11-22 10:19   ` Rainer Orth
2019-02-26 15:14     ` Rainer Orth
2019-02-26 16:09       ` Pedro Alves
2019-02-26 20:03         ` Rainer Orth
2019-02-28 15:16           ` Rainer Orth
2019-03-05 15:47             ` Tom Tromey
2019-03-05 18:58               ` Pedro Alves

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=5e65ba26-c0b6-ab77-a682-933f3bcd1827@ericsson.com \
    --to=simon.marchi@ericsson.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=phantall@gmail.com \
    --cc=ro@cebitec.uni-bielefeld.de \
    /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).