public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: dumper does not produce core that gdb recognizes?
Date: Sat, 9 Jul 2022 14:23:31 +0000	[thread overview]
Message-ID: <DM8PR09MB7095D1598FD87168EED4A9FFA5859@DM8PR09MB7095.namprd09.prod.outlook.com> (raw)

> I've learned that once I get a setup that seems to be stable

That's what I thought about my 3.2.0 setup, too, but following your own
conclusions about the rolling release, one can never be sure...

Anyways, maybe it's time for me to upgrade.  I did not because it looked
like 3.3 was coming out with a lot of new issues (as people were reporting),
so I just froze all upgrades.  Looks like 3.3 is now stabilized as 3.4 is
getting ready LOL

> This was fixed in gdb-10.1-1 [1] (upstream in gdb 11) and cygwin 3.1.7.

Well, I've got cygwin 3.2.0 (which supposedly was expected to be "good" already)
yet gdb 9.2 at the same time...  Oh well, that rolling release...

Thanks for all the replies, though, I really appreciate it!

Anton Lavrentiev
Contractor NIH/NLM/NCBI

             reply	other threads:[~2022-07-09 14:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09 14:23 Lavrentiev, Anton (NIH/NLM/NCBI) [C] [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-09  0:58 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-09  1:31 ` Backwoods BC
2022-07-09  6:30   ` Brian Inglis
2022-07-09 10:00 ` Jon Turney
2022-07-08 22:06 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-08 22:53 ` 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=DM8PR09MB7095D1598FD87168EED4A9FFA5859@DM8PR09MB7095.namprd09.prod.outlook.com \
    --to=lavr@ncbi.nlm.nih.gov \
    --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).