From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-announce@cygwin.com
Subject: gdb-10.1-1 (TEST)
Date: Sat, 24 Oct 2020 19:33:00 +0100 [thread overview]
Message-ID: <9cda26c2-5697-8cb5-4c35-a27e564f3574@dronecode.org.uk> (raw)
The following package has been updated in the Cygwin distribution:
* gdb-10.1-1
The GNU debugger allows you to debug programs written in C, C++, and
other languages, by executing them in a controlled fashion and printing
their data.
This is an update to the latest upstream version:
https://sourceware.org/pipermail/gdb-announce/2020/000126.html
See the /usr/share/doc/gdb/NEWS file for a list of user-visible changes.
* GDB can now differentiate between "Windows" and "Cygwin" ABIs.
gdb understands these ABIs differ, in that x86_64 Cygwin is LP64, but
x86_64 Windows is LLP64, and that different signal numbers are used by
Cygwin and MinGW runtimes.
For example, this should mean that 'print sizeof(long)' now gives the
correct result for a x86_64 Cygwin inferior.
The detected ABI for an inferior can be inspected with 'show osabi'.
* gdb now supports debugging a 32-bit Windows program using a 64-bit
Windows GDB (Not likely to work correctly for Cygwin programs).
In addition, it contains the following patches carried forward from the
previous Cygwin package:
* Teach the demangler to deal with '@'-decorated __stdcall functions
* (experimental) Teach gdb how to unwind frames for the Cygwin signal
delivery wrapper functions _sigbe and sigdelayed
* Fix a memory leak which would occur in the case when the result of
realpath() is greater than or equal to SO_NAME_MAX_PATH_SIZE (Corinna
Vinschen)
and the following new patches:
* Handle x86_64 Cygwin core dumps (when generated by dumper from Cygwin
3.1.7 or later)
* Simplify and improve handling of inferior context after a Cygwin signal
reply other threads:[~2020-10-24 18:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9cda26c2-5697-8cb5-4c35-a27e564f3574@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-announce@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).