public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Cc: "Rockefeller, Harry" <Harry.Rockefeller@flightsafety.com>
Subject: Re: gdb 7.11.1-2 started within emacs fails
Date: Wed, 11 Oct 2017 19:44:00 -0000	[thread overview]
Message-ID: <9bed0b67-2930-ee6b-8361-4bf4d9d7d542@dronecode.org.uk> (raw)
In-Reply-To: <207e93bf-8f7e-57a3-1abc-cc645c79020c@cornell.edu>

On 27/09/2016 21:15, Ken Brown wrote:
> On 9/27/2016 2:47 PM, Rockefeller, Harry wrote:
>> Using program foo:
>>       program foo
>>       e = 1.0
>>       stop
>>       end
>>
>> $ /usr/bin/gfortran    -g foo.f -o foo
>>
>> Emacs version info: GNU Emacs 25.1.1 (i686-pc-cygwin, GTK+ Version 
>> 3.18.9) of 2016-09-17
>>
>> Inside emacs I ran M-x gud-gdb and got
>> ... GNU gdb (GDB) (Cygwin 7.11.1-2) 7.11.1 ...
>> (gdb) b 1
>> Breakpoint 1 at 0x4011d6: file foo.f, line 1.
>> (gdb) r
>> Starting program: /cygdrive/c/Users/harryr/foo.exe
>> [New Thread 6296.0x22ac]
>> [New Thread 6296.0x24d4]
>> readline: readline_callback_read_char() called with no handler!
>> Debugger aborted (core dumped)
>>
>> Foo written in C++ also fails with the same message.
>> Running gdb foo in bash gives the expected result:
>> gdb stops at first executable line prompting for next gdb command.
> 
> I can confirm that this happens also with gdb-7.11.1-1 but not 
> gdb-7.10.1-1.  (I tested on x86_64, since gdb-7.10.1-1 is broken on x86.)
> 
> It also fails with M-x gdb instead of M-x gud-gdb, but with a different 
> error message:
> 
>    Failed to resume program execution (ContinueDebugEvent failed, error 87)

These problem seem not longer occur due to upstream changes in gdb 7.12.

I've uploaded a gdb 7.12.1-1 test package.

--
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

  parent reply	other threads:[~2017-10-11 19:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-27 20:03 Rockefeller, Harry
2016-09-27 20:32 ` Ken Brown
2016-09-29 17:24   ` Rockefeller, Harry
2016-10-19 16:47     ` William M. (Mike) Miller
2016-10-19 16:54       ` Rockefeller, Harry
2016-10-19 17:03         ` Corinna Vinschen
2016-10-19 19:21           ` William M. (Mike) Miller
2016-10-20 19:06         ` Jon Turney
2017-10-11 19:44   ` Jon Turney [this message]
2017-10-11 20:32     ` Ken Brown
2017-10-12 17:24       ` Jon Turney
2017-10-12 19:47         ` Ken Brown

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=9bed0b67-2930-ee6b-8361-4bf4d9d7d542@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).