assert creates unusable core dump on current stable Cygwin release

Brian Inglis Brian.Inglis@SystematicSw.ab.ca
Thu Oct 10 22:20:00 GMT 2019


On 2019-10-10 14:57, Csaba Raduly wrote:
> On Thu, Oct 10, 2019 at 9:19 PM Jon Turney  wrote:
>> (and I guess this patch is not acceptable as-is, as it looks like it
>> would break x86)
> That was my reaction too.

Obviously there would have to be some arch dependent conditional changes, but I
was hoping that someone with a clue about libbfd, could provide some hints as to
where else to look for more info on what other changes might be required, or
confirmation that this is object oriented enough to mainly just work with some
additional tweaks.

I also found out, and found a mailing list post that confirmed, that gdb gcore
also does not work to generate a core image on Windows, as that was my next
place to look.

So it looks like gdb gcore for x86 could be implemented by adding the dumper code.

The question is where to ask or look to figure out what Windows x86_64 needs
over what Windows x86 needs, and add that to both gdb gcore and dumper, as gdb
seems to handle debugging and debuginfo fine.
If this could be derived from say, Cygwin ld libbfd calls, or the diffs between
x86 and x86_64 ld.bfd calls, or nm, objcopy, objdump etc. diffs, I could look at
doing that.
I'm not sure I'd want to have to understand in detail how Windows puts its exes
together to get started.

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

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple



More information about the Cygwin mailing list