From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Subject: Re: gdb 7.11.1-2 started within emacs fails
Date: Thu, 20 Oct 2016 19:06:00 -0000 [thread overview]
Message-ID: <5e89687c-41fc-b7ee-55af-4f32b52ced9b@dronecode.org.uk> (raw)
In-Reply-To: <cf9fc69a153f41f7b4c0296774a85f96@vsrv060ex03.ssd.fsi.com>
On 19/10/2016 17:46, Rockefeller, Harry wrote:
>>>> 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.
>
> No progress I am aware of. I switched over to 64-bit Cygwin which uses gdb-7.10.1-1 to avoid this problem.
I've done some investigation, and the problem seems to be that when run
from emacs or ddd, the inferior process doesn't end up in it's own
process group, but I haven't made any progress on why that is happening.
per [1], I think I've fixed the problem with x86 and gdb-7.10.1-1, so it
should no longer be necessary to use gdb-7.11.1 to avoid those problems,
but obviously this needs to be fixed at some point...
[1] https://cygwin.com/ml/cygwin/2016-10/msg00243.html
--
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
next prev parent reply other threads:[~2016-10-20 14:08 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 [this message]
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=5e89687c-41fc-b7ee-55af-4f32b52ced9b@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).