From: "William M. (Mike) Miller" <william.m.miller@gmail.com>
To: cygwin@cygwin.com
Subject: Re: emacs gud-interface is not updated after gdb command execution (maybe because of incomplete output from gdb)
Date: Thu, 26 May 2016 15:48:00 -0000 [thread overview]
Message-ID: <CAH5rLZXZBreNGeSPbLw3Z7EhRF=muRzzLPXU7RqJXWvzubE2Pg@mail.gmail.com> (raw)
In-Reply-To: <466943424.37628.394d161a-7219-415d-a659-0f774811ad2d.open-xchange@email.1und1.de>
On Thu, May 26, 2016 at 5:30 AM, Tobias Zawada <i_inbox@tn-home.de> wrote:
> Hello,
> when debugging c-programs (the special program does not matter) with gud/gdb the
> prompt "(gdb)"
> is missing after the execution of the "start" command. This also happens with
> other commands such as "next". Also variable values and outputs are not
> correctly updated.
> I do not have this problem under linux.
>
> There was already a similar problem with the update of the gdb-interface:
> https://www.cygwin.com/ml/cygwin/2015-06/msg00277.html
> That thread has a dead end.
As the initiator of that thread, thank you very much for bringing up
the issue again and for all the investigative work. Since my initial
report did not result in any fixes, I have given up on gud and am
using cgdb, which is inferior but works well enough, but it would be
very welcome to have a fully-working gud again.
Just one update on that original report: item #3 has been fixed by
recent versions of gdb and is no longer a problem.
--
William M. (Mike) Miller | Edison Design Group
william.m.miller@gmail.com
--
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-05-26 11:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 12:32 Tobias Zawada
2016-05-26 15:48 ` William M. (Mike) Miller [this message]
2016-05-26 17:48 ` Ken Brown
2016-05-26 18:00 ` Tobias Zawada
2016-05-26 18:01 ` Ken Brown
2016-05-31 1:47 ` gdb pty problem [Was: emacs gud-interface is not updated after gdb command execution (maybe because of incomplete output from gdb)] Ken Brown
2016-05-31 9:35 ` Ken Brown
2016-05-31 22:41 ` Corinna Vinschen
2016-06-01 12:51 ` Ken Brown
2016-06-01 13:02 ` Ken Brown
2016-06-01 14:28 ` Corinna Vinschen
2016-06-01 14:29 ` Corinna Vinschen
2016-06-01 14:33 ` Ken Brown
2016-06-01 15:22 ` Ken Brown
2016-06-01 18:29 ` Corinna Vinschen
2016-06-01 19:05 ` Ken Brown
2016-06-01 19:54 ` Corinna Vinschen
2016-06-01 20:01 ` Ken Brown
2016-06-01 21:05 ` [GOLDSTAR] " Corinna Vinschen
2016-06-02 2:09 ` Andrew Schulman
2016-06-01 14:18 ` Corinna Vinschen
2016-06-06 10:12 ` Takashi Yano
2016-06-06 13:16 ` Corinna Vinschen
2016-06-07 13:14 ` Takashi Yano
2016-06-07 16:11 ` Corinna Vinschen
2016-06-06 14:01 ` 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='CAH5rLZXZBreNGeSPbLw3Z7EhRF=muRzzLPXU7RqJXWvzubE2Pg@mail.gmail.com' \
--to=william.m.miller@gmail.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).