public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>,
	The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: dumper does not produce core that gdb recognizes?
Date: Sat, 9 Jul 2022 11:00:29 +0100	[thread overview]
Message-ID: <359ba48f-5480-2ca5-84e0-50e1f1ac8141@dronecode.org.uk> (raw)
In-Reply-To: <DM8PR09MB709546504D09F5207B1D4635A5859@DM8PR09MB7095.namprd09.prod.outlook.com>

On 09/07/2022 01:58, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
>> The latest version of gdb that is not a test version is 11.2. But
>> you are using 9.2.
> 
> I am using the older dumper as well, my working cygwin is not cutting edge.
> 
> $ dumper -V
> dumper (cygwin) 3.2.0
> 
> What I am coming at is that if dumper is not consistent with gdb,
> that does not make any sense.  They should always be consistent at
> any given time, so if the packages (dumper's and gdb's) installed together,
> they would be able to cooperate. 

Ideally, that would be the case.

Unfortunately, for a long time, on x86_64, dumper wasn't working 
correctly, and gdb couldn't read those dumps, and nobody cared enough to 
do anything about it.

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

If you choose to use earlier versions on x86_64, it's a known defect 
that it won't work.

[1] https://cygwin.com/pipermail/cygwin-announce/2020-October/009752.html

  parent reply	other threads:[~2022-07-09 10:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-09 14:23 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
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=359ba48f-5480-2ca5-84e0-50e1f1ac8141@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    --cc=lavr@ncbi.nlm.nih.gov \
    /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).