From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: Ken Brown <kbrown@cornell.edu>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: [EXTERNAL] Re: dumper does not produce core that gdb recognizes?
Date: Fri, 8 Jul 2022 23:09:27 +0000 [thread overview]
Message-ID: <DM8PR09MB7095CB60032523FD08EA4ECFA5829@DM8PR09MB7095.namprd09.prod.outlook.com> (raw)
In-Reply-To: <308d675e-84a8-6d53-6ea9-a5a3abb258c6@cornell.edu>
> 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 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!
Anton Lavrentiev
Contractor NIH/NLM/NCBI
next prev parent reply other threads:[~2022-07-08 23:10 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 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] [this message]
2022-07-09 0:22 ` [EXTERNAL] " Takashi Yano
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=DM8PR09MB7095CB60032523FD08EA4ECFA5829@DM8PR09MB7095.namprd09.prod.outlook.com \
--to=lavr@ncbi.nlm.nih.gov \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).