From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: dumper does not produce core that gdb recognizes?
Date: Sat, 9 Jul 2022 00:30:21 -0600 [thread overview]
Message-ID: <6a6492a6-42d6-5ae4-4594-9312e41f2fce@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAKwdsS_01n8A=7BPurjmmrr9sMqaKv+gzGY2UO8_WGSUX+OhNw@mail.gmail.com>
On 2022-07-08 19:31, Backwoods BC wrote:
> On Fri, Jul 8, 2022 at 5:59 PM Lavrentiev, Anton (NIH/NLM/NCBI) 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.
> I've encountered similar issues with other things in Cygwin. The fact
> that it is a rolling release means that there is no such thing as a
> stable release. I've been using Cygwin for at least 20 years and I've
> learned that once I get a setup that seems to be stable, I do not
> upgrade anything unless there is a very pressing reason to do so.
You have a few moving parts in the chain here - binutils, gcc, gdb,
dumper (cygwin), and Windows, that are all being updated asynchronously,
and have to use and handle features provided by each other, so parts are
always out of sync, and need tweaked to keep up.
As this is a volunteer project, toolchain internals are complex and
takes time to understand, comprehension, knowledge, experience are rare,
and time is scarce, dumper sometimes lags to the detriment of
debuggability.
> This is a pain in the butt, but it is what it is. I still find that
> Cygwin is better suited than WSL for my primary needs of writing
> scripts and filters to make my life in Windows easier.
WSL adds its own issues. I found if I want to compare (with) Linux
distros and behaviours, I need to use VMs.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2022-07-09 6:30 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 [this message]
2022-07-09 10:00 ` Jon Turney
-- 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=6a6492a6-42d6-5ae4-4594-9312e41f2fce@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).