public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: [EXTERNAL] Re: dumper does not produce core that gdb recognizes?
Date: Sat, 9 Jul 2022 09:22:51 +0900	[thread overview]
Message-ID: <20220709092251.a7a946962f44576fc915168c@nifty.ne.jp> (raw)
In-Reply-To: <DM8PR09MB7095CB60032523FD08EA4ECFA5829@DM8PR09MB7095.namprd09.prod.outlook.com>

On Fri, 8 Jul 2022 23:09:27 +0000
"Lavrentiev, Anton \(NIH/NLM/NCBI\) \[C\] wrote:
> > Try using a more recent gdb.  I just tried your test case with gdb-12.1-1
> > (available as a test release), and it seemed to work.
> 
> Thanks for the quick response...  Though I'd rather not use test releases.

The latest version of gdb that is not a test version is 11.2. But
you are using 9.2.

> The dumper binary and gdb in my case are supposed to be consistent with each other
> (installed from the set of release packages on the same day via setup)...  So I don't
> really understand the discrepancy here:  are you saying that dumper can produce a core
> that current gdb cannot read?  But that's bizarre!

Even if so, the combination of latest dumper.exe (in cygwin 3.3.5
package) and gdb 11.2 do not have such a problem. Therefore, we
have nothing to do for that.

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 22:06 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-08 22:53 ` Ken Brown
2022-07-08 23:09   ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-07-09  0:22     ` Takashi Yano [this message]

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=20220709092251.a7a946962f44576fc915168c@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --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).