public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Cc: "Rockefeller, Harry" <Harry.Rockefeller@flightsafety.com>
Subject: Re: gdb input error gfortrani_fbuf_read () cyggfortran-3.dll
Date: Tue, 27 Sep 2016 15:14:00 -0000	[thread overview]
Message-ID: <8bb12fde-de72-2524-ee5c-1cf8f9b99ece@dronecode.org.uk> (raw)
In-Reply-To: <af5cbdfb-21ab-8450-f089-0d1af5c26ea1@dronecode.org.uk>

On 26/09/2016 14:41, Jon Turney wrote:
> On 22/09/2016 20:55, Rockefeller, Harry wrote:
>> gdb (test version) and program's 'read' seem to have an input clash.
>> Anyway, gdb used to pause and allow keyboard input.
>
> Thanks for reporting this problem, and the test case.
>
>> Thread 1 "foo" hit Breakpoint 1, foo () at foo.f:4
>> 4             write(*,*) "Enter a real number"
>> (gdb) n
>>  Enter a real number
>> 5             read(*,*) e
>> (gdb) n
>>
>> [1]+  Stopped                 gdb foo
>>
>> $ fg
>> gdb foo
>>
>> Thread 1 "foo" received signal SIGTTIN, Stopped (tty input).
>> 0x5bd015dc in gfortrani_fbuf_read () from /usr/bin/cyggfortran-3.dll
>
> In gdb 7.11 there are some upstream changes in the way access to the
> controlling terminal is given the inferior, and I guess this has broken
> something here.

I uploaded a gdb 7.11.1-2 test package with a fix for this.



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2016-09-27 15:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22 20:35 Rockefeller, Harry
2016-09-26 15:08 ` Jon Turney
2016-09-27 15:14   ` Jon Turney [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=8bb12fde-de72-2524-ee5c-1cf8f9b99ece@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=Harry.Rockefeller@flightsafety.com \
    --cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).