public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: gdb not working properly in Cygwin
Date: Thu, 21 Jan 2021 18:30:49 -0500	[thread overview]
Message-ID: <2710d0d7-e249-a166-ad1c-de7c1ed2a3e0@cornell.edu> (raw)
In-Reply-To: <CAM25FTp7DieHYOdfQeFoNNjq+24pG9JPX8O-c6Hk8oZ3RX25Aw@mail.gmail.com>

On 1/21/2021 5:27 PM, Tord Andreasson via Cygwin wrote:
> Hi,
> 
> I encounter the same issue too.
> 
> gdb starts however there is no gdb prompt, nothing is echoed and nothing is
> printed on the bash window except an empty blank line. From now you operate
> blindfolded.
> 
> Debugging a simple application that prints "Hello World" on file
> demonstrates that gdb loads the application and is responsive to commands;
> "run" will run the program to its completion, and "quit" will return to the
> bash prompt.
> 
> I tried "strace -o /tmp/gdb.strace /usr/bin/gdb --version" and indeed there
> are lines with 37 error messages in it. Since the trace file is large (2MB)
> I have extracted the lines containing the error messages and attached them
> to this email. I can attach the full gdb.strace if that is needed.
> 
> I have no insight into what these errors are and how to remedy or
> workaround them, any help would be appreciated.

Many errors are to be expected, so your excerpt of gdb.strace doesn't really 
tell us much.  Please post the full strace output somewhere.  And please send 
cygcheck output *as an attachment* as instructed here:

   https://cygwin.com/problems.html

Ken



  parent reply	other threads:[~2021-01-21 23:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 19:02 Daniel, Barry K.
2021-01-21 19:08 ` Marco Atzeri
2021-01-21 22:27   ` Tord Andreasson
2021-01-21 23:01     ` matthew patton
2021-01-21 23:30     ` Ken Brown [this message]
2021-02-03 21:40       ` Marco Atzeri
2021-02-03 22:06         ` Marco Atzeri

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=2710d0d7-e249-a166-ad1c-de7c1ed2a3e0@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).