Ken Brown via Cygwin wrote:
On 6/28/2020 9:31 AM, Jon Turney wrote:
On 28/06/2020 01:50, Ken Brown via Cygwin wrote:
Following the instructions at
https://cygwin.com/cygwin-ug-net/using-cygwinenv.html, I tried to create a
core file that I could examine with gdb, but I apparently ran into a gdb bug.
I tried both gdb 9.2-1 and 8.3.1-1. Here are the results with 9.2-1.
[...]
Unfortunately, I think dumper doesn't produce anything useful on x86_64. See
[1] et seq.
Thanks. Sorry I didn't notice that people had asked the same question before.
We should probably fix the documentation:
https://cygwin.com/cygwin-ug-net/using-cygwinenv.html
https://cygwin.com/cygwin-ug-net/dumper.html
Or maybe we should just remove all mention of dumper from the documentation.
Given that we're trying to move people away from 32-bit Cygwin, I don't think it
makes sense to document a feature that works only on the latter.
I hesitate to comment when I can't immediately work on this, but, ...making
dumper work on 64-bit Cygwin is on my TODO list but not right at the top. It
would be helpful to keep the program around in its current 32-bit state as a
template for 64-bit.
Re the documentation, I do think the first example should probably not mention
dumper, or should parenthetically add "(32-bit only)". The second example doc
should say somewhere that the tool is currently 32-bit only. In addition, the
current dumper should probably detect when it's running in the wrong environment
and stop with an error, rather than running as if it's doing something useful.
Whatever is decided for the short term, I can make time to implement that.
..mark
P.S. For the long term, I think it was Jon who suggested dumper generate Windows
minidumps rather than the current Frankensteinish dumps. I intend to
investigate that when I get to this project.
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
