Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Make attach_command exception-safe
Date: Fri, 29 Aug 2008 15:23:00 -0000	[thread overview]
Message-ID: <20080829142418.GA15675@caradoc.them.org> (raw)
In-Reply-To: <200808291110.43091.vladimir@codesourcery.com>

On Fri, Aug 29, 2008 at 07:10:42AM +0000, Vladimir Prus wrote:
> 
> When attach_command executes, it might disable stdin. It further might
> throw, and does not enable stdin in that case. For CLI case, top-level
> event loop will catch the exception and enable stdin. For MI case, MI
> interpreter catches the exception in order to print the error message,
> and of course it has no idea about any stdin disabling.
> 
> This patch makes attach_command exception-safe, enabling stdin on
> throw.
> 
> OK?

OK.

>  ChangeLog.csl |    6 ++++++

Not that bit :-)

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-08-29 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-29  7:11 Vladimir Prus
2008-08-29 15:23 ` Daniel Jacobowitz [this message]
2008-11-03 21:08   ` Vladimir Prus

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=20080829142418.GA15675@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.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