public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-announce@cygwin.com
Subject: gdb 14.1-1 (TEST)
Date: Tue, 12 Dec 2023 18:30:47 +0000	[thread overview]
Message-ID: <e29f34a4-8a17-466c-9cbb-1c577b0953cd@dronecode.org.uk> (raw)


The following packages have been uploaded to the Cygwin distribution:

* gdb-14.1-1
* gdb-debuginfo-14.1-1
* gdb-multiarch-14.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/2023/000137.html

See the /usr/share/doc/gdb/NEWS file for a list of user-visible changes.

This release adds a separate package containing a gdb built with 
multiarch support for cross-debugging by connecting to a gdbserver 
running on a different architecture.

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)
* Simplify and improve handling of inferior context after a Cygwin signal
* Use cygwin pgid if inferior is a cygwin process (Takashi Yano)

                 reply	other threads:[~2023-12-12 18:30 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=e29f34a4-8a17-466c-9cbb-1c577b0953cd@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).