From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-announce@cygwin.com
Subject: gdb-7.12.1-2 (TEST)
Date: Thu, 12 Oct 2017 17:25:00 -0000 [thread overview]
Message-ID: <0f99023c-1a5d-1f77-8ee1-7c54be946295@dronecode.org.uk> (raw)
In-Reply-To: <dd5d7f03-01d2-00f7-c127-fe8f8fb35312@dronecode.org.uk>
The following package has been updated in the Cygwin distribution:
* gdb-7.12.1-2
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.
Changes since 7.12.1-1:
* 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:
2d2891587aa3af5bc45dba054a68931e80e7cfc150ce3bd335b5825f9fb2a3967f5fb23e14aee49756500f7906959b233718bd3e0ed363c0a24e8f524be59a19
*gdb-7.12.1-2-src.tar.xz
f3c690671d04ae9a1a8c2ebe34b7ce1fe61efe1f119c45e4658b9fa397f635a340e0ea9d83574890177b18a5bf50157f7fa10c364fb19bebd8a7c2bb5f83fa90
*gdb-7.12.1-2.tar.xz
ab37b029156fc01bee494a9b8d9daab51c3c3cb5ded8210ee1ed0382364f13d8d74ca60c84433ff1d765ced9146a55f71b94ef9a96231cc809406da4126a1049
*gdb-debuginfo-7.12.1-2.tar.xz
x86_64:
c8b5995246f2a736fa1df76c19c9cc488d2a28f87aea137fab18f5b743a369b4c410c5503dd49cfeb91fb1a64bb7672272d77283800154aa1c321fc932c809fd
*gdb-7.12.1-2-src.tar.xz
1b05a98a4435ee98a46d19b0d875f8e43f38fcf3ccf265e1c1e4b2539ee0026ff1ea19f6a20ffd21a2b51942e508114a9650ab15f01fb719fa2995bc233050ef
*gdb-7.12.1-2.tar.xz
b3fcfa5dd16cbc8d2ddbd869f164f5add593997fc413301ef0aa199f9ce336dee313a39f4b74de60c5cf94cb32ae651ec1cce13eecf862c9eba0d15b8ecfc0a3
*gdb-debuginfo-7.12.1-2.tar.xz
prev parent reply other threads:[~2017-10-12 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 19:43 gdb-7.12.1-1 (TEST) Jon Turney
2017-10-12 17:25 ` Jon Turney [this message]
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=0f99023c-1a5d-1f77-8ee1-7c54be946295@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).