On 28/01/2020 15:40, Rockefeller, Harry wrote:
Since you and I appear to be the only ones interested in this particular
problem I brought this off the
Cygwin list, at least for now.
Please don't do this.
https://cygwin.com/problems.html#personal-email
You are correct, and I am able to repro
On 27/01/2020 16:44, Rockefeller, Harry wrote:
I don't know if this is a gdb or a Cygwin implementation of gdb that is a
problem.
Since I can go back to gdb version 8.1.1-1 this is not a problem for me now.
Here is a test case using the Fortran source above:
$ gfortran -g test1.f -o test1.exe
[snip]
>>>I'm not able to reproduce this problem. Perhaps you can provide a similar
>>>transcript showing the steps to reproduce?
[snip]
>>Test code:
> >program test
>>implicit none
>> realcycle_time_preset /0.0/ ! (seconds)
>> realcycle_length /0.0/ ! (seconds)
>-Original Message-
> From: cygwin-ow...@cygwin.com On Behalf Of
> Rockefeller, Harry
>Sent: Friday, January 17, 2020 11:35 AM
>To: Jon Turney ; The Cygwin Mailing List
>
>Subject: RE: cin and read(*,*) not waiting for kbd input in gdb
>>>-Original Me
>>-Original Message-
>>From: Jon Turney
>Sent: Friday, January 17, 2020 9:40 AM
>To: The Cygwin Mailing List
>Cc: Rockefeller, Harry
>Subject: Re: cin and read(*,*) not waiting for kbd input in gdb
>EXTERNAL EMAIL: STOP and verify sender address, links, and
On 16/01/2020 21:02, Rockefeller, Harry wrote:
Both the Fortran and cpp used to work correctly when run in gdb.
Thanks for reporting this problem.
I assume this means that this worked with gdb-8.1.1-1, but not with
gdb-8.2.1-1 (Made available for testing 2019-03-21 [1], promoted to
current 2
6 matches
Mail list logo
