dumper does not produce core that gdb recognizes?

[Brian Inglis]

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.]