public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "William M. (Mike) Miller" <william.m.miller@gmail.com>
To: cygwin@cygwin.com
Subject: Emacs gud not working on new installation
Date: Wed, 04 Mar 2020 15:39:00 -0000	[thread overview]
Message-ID: <CAH5rLZVFq1PVHvvMx4SH+-KWaUCtoBi9j80z6PBKKTpSpFzRAA@mail.gmail.com> (raw)

I installed Cygwin on a new computer last weekend. On my previous computer,
I used gud with gdb in emacs (M-x gdb) for debugging. However, on the new
computer it is not working. I suspect that gdb is producing output that is
not formatted correctly for gud to parse.

When I start gud in emacs on the new computer, I get the usual 6-pane
configuration, and gdb puts out its usual configuration and start-up
information. When I type the "run" command, however, the program being
debugged starts and runs, the command pane correctly displays the usual
"Starting program" messaged, but the "[New thread...", etc. messages and
any further gdb output (breakpoint messages, output of "info", etc.) do
not. The program input/output pane updates, but none of the others do. I
can type commands that are correctly passed through to gdb, but no gdb
output ever appears in the command pane.

I also tried just the plain "M-x gud-gdb" interface, and that may give a
hint as to what is going on. I did get the gdb output, but with only
newlines, no carriage returns, in the command pane. That is, each
successive line of output from gdb began one character to the right of the
last character of the previous line instead of beginning in column 0, as it
did on the old computer.

Any suggestions for how to diagnose or fix the problem would be most
appreciated.

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

             reply	other threads:[~2020-03-04 14:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04 15:39 William M. (Mike) Miller [this message]
2020-03-04 15:59 ` Ken Brown
2020-03-04 18:16   ` William M. (Mike) Miller
2020-03-05 13:05     ` Takashi Yano
2020-03-05 14:27       ` William M. (Mike) Miller

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=CAH5rLZVFq1PVHvvMx4SH+-KWaUCtoBi9j80z6PBKKTpSpFzRAA@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).