From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-announce@cygwin.com
Subject: gdb-8.0.1-1 (TEST)
Date: Sat, 14 Jul 2018 12:45:00 -0000 [thread overview]
Message-ID: <bd10e6d8-adf0-f793-1bd6-f79f1e63fb8b@dronecode.org.uk> (raw)
The following package has been updated in the Cygwin distribution:
* gdb-8.0.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 a later upstream version:
https://sourceware.org/ml/gdb-announce/2017/msg00004.html
See the /usr/share/doc/gdb/NEWS file for a list of user-visible changes.
In addition, it contains the following patches carried forward from the
previous Cygwin package:
* Teach the demangler to deal with '@'-decorated __stdcall functions
* Various fixes for Cygwin signal handling
* (experimental) Teach gdb how to unwind frames for the Cygwin signal
delivery wrapper functions _sigbe and sigdelayed
* Warn rather than stopping with an error if realpath() for a DLL fails
(Tim Chick)
Addresses: https://cygwin.com/ml/cygwin/2014-08/msg00401.html
* 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)
* Fix inferior stopping with SIGTTIN, if it tries to read from the
terminal after it has been continued
Addresses: https://cygwin.com/ml/cygwin/2016-09/msg00285.html
* Workaround https://sourceware.org/bugzilla/show_bug.cgi?id=21078 by
linking with shared libstc++ and libgcc.
Addresses: https://cygwin.com/ml/cygwin/2017-10/msg00109.html
x86:
7975309cd6f9f1f7e5fb109d3b1511aa749bc3aa3816a9ecc9ee2f57792c9e637b878e36f5485fd639e422d1145a91ecb836337a4884b2259c279da1d865db1d
*gdb-8.0.1-1-src.tar.xz
af6eec52bb7194c59127391564e7330dfd322b442e53b28492b95285139698294a7b317115942a78831d0cb54e802310d2cbcc06df674f61f659d6b2fe27e924
*gdb-8.0.1-1.tar.xz
6477438617a400e22467754acd0c01fd8c8852af0e3cd38f1da82a26306a6a57d92051aa2b15be5b05f52ee8db6430bf8c69da2e66d534dfb3275b9a9827d5f0
*gdb-debuginfo-8.0.1-1.tar.xz
x86_64:
b88c08572cad31a6f6807be532319461af18a69a79491f93809854a7d5113871e6c7880e65193d572515cd61a837157c35641a61cf90d5a92a655f99d31849ca
*gdb-8.0.1-1-src.tar.xz
a6543fff99a16816dfa8bab7884256f7cfef810303edf3cc27111e9e1379641d72f61d97099d886f44277d1445871f71a7f93635e71855e88c6d43e39ec27446
*gdb-8.0.1-1.tar.xz
3a6847dbb86e3d50a033e2ceb1d08ed9978a39ba1516fb18423e05630cde07d36236987fc96be06a9783decc112cb6c3565f865b85491cd0189b214a7e8a44c3
*gdb-debuginfo-8.0.1-1.tar.xz
reply other threads:[~2018-07-14 12:45 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=bd10e6d8-adf0-f793-1bd6-f79f1e63fb8b@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-announce@cygwin.com \
--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).