Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Matt Rice <ratmice@gmail.com>,
	Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: [patch] Fix target-async SIGTTOU stop (PR 12260)
Date: Mon, 29 Aug 2011 15:17:00 -0000	[thread overview]
Message-ID: <201108291617.25592.pedro@codesourcery.com> (raw)
In-Reply-To: <CACTLOFrx3wqjz0ch6objbTyGfnukFo359=YhLbXpnFAROHMu-w@mail.gmail.com>

On Wednesday 24 August 2011 06:24:36, Matt Rice wrote:
> On Tue, Aug 23, 2011 at 12:31 PM, Jan Kratochvil
> <jan.kratochvil@redhat.com> wrote:
> > Hi,
> >
> > it is difficult to play with `set target-async on' as it usually SIGTTOU stops
> > at various places.
> > http://sourceware.org/bugzilla/show_bug.cgi?id=12260
> >
> > $ ./gdb -nx -ex 'set target-async on' -ex start ./gdb
> > [...]
> > Starting program: .../gdb/gdb
> > [1]+  Stopped                 ./gdb -nx -ex 'set target-async on' -ex start ./gdb
> >
> > If it has a regression it IMO only means there is missing
> > target_terminal_inferior call at some other place.
> >
> > No regressions on {x86_64,x86_64-m32,i686}-fedora16pre-linux-gnu.  But I was
> > unable to reproduce the problem under DejaGnu so the regression test may not
> > be meaningful.
> >
> > Not going to check it in without a review.
> >
> 
> Not really a review, just thought i'd mention this is also fixed by
> the following patch
> http://sourceware.org/ml/gdb-patches/2011-08/msg00235.html

I was going to look at Jan's patch, and I'm a bit confused on the state
of things, and the state of Matt's patch --- there was a follow up, which
had a problem.  Is the msg00235.html version the final one instead?

> this also fixes the original report of PR 10720 which seems to be a
> dupe, not sure about the latter reports in 10720.
> the test cases i added do not cover this either.

By "this" you mean Jan's or yours?

> 
> to quote from elsewhere in that thread
> matt> more information on PR 10720, which I'd had random difficulties
> matt> reproducing, I managed to figure out why, the process being attached
> matt> to must be on the same tty as the gdb process to reproduce it.
> matt> Haven't been able to reproduce that in the testsuite though.
> 
> my guess is that deja-gnu doesn't meet this requirement to be able to
> reproduce it.
> 

-- 
Pedro Alves


  reply	other threads:[~2011-08-29 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-23 19:32 Jan Kratochvil
2011-08-24  5:24 ` Matt Rice
2011-08-29 15:17   ` Pedro Alves [this message]
2011-08-29 15:26     ` Matt Rice
2011-09-23 16:33 ` cancel/resolved: " Jan Kratochvil

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=201108291617.25592.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=ratmice@gmail.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