From: "Rockefeller, Harry" <Harry.Rockefeller@flightsafety.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: gdb 7.11.1-2 started within emacs fails
Date: Wed, 19 Oct 2016 16:54:00 -0000 [thread overview]
Message-ID: <cf9fc69a153f41f7b4c0296774a85f96@vsrv060ex03.ssd.fsi.com> (raw)
In-Reply-To: <CAH5rLZU9808GtL8KeaZYrYS0zrORyJXE4+jyiBNmFoSccd-z3g@mail.gmail.com>
>-----Original Message-----
>From: cygwin-owner@cygwin.com [mailto:cygwin->owner@cygwin.com] On Behalf Of William M. (Mike) Miller
>Sent: Wednesday, October 19, 2016 10:30 AM
>To: cygwin@cygwin.com
>Subject: Re: gdb 7.11.1-2 started within emacs fails
[snip]
>>>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) Ken
>>
>> I tried using 'ddd' instead of emacs and gdb aborts with the same readline ... message above.
>Any progress on the above issue? I recently updated my gdb and am running into the same problem.
>William M. (Mike) Miller | Edison Design Group william.m.miller@gmail.com
No progress I am aware of. I switched over to 64-bit Cygwin which uses gdb-7.10.1-1 to avoid this problem.
This "request" may be related to the problem: I would like to see the autogenerated gdb line:
"---Type <return> to continue, or q <return> to quit---" to go away.
gdb pauses posting this line unnecessarily.
next prev parent reply other threads:[~2016-10-19 16:47 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 [this message]
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
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=cf9fc69a153f41f7b4c0296774a85f96@vsrv060ex03.ssd.fsi.com \
--to=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).