Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 11.0.90 available for testing
Date: Thu, 08 Jul 2021 19:39:48 +0300	[thread overview]
Message-ID: <83zguwdajv.fsf@gnu.org> (raw)
In-Reply-To: <20210703184833.94F2889AFF@takamaka.home> (message from Joel Brobecker on Sat, 3 Jul 2021 11:48:33 -0700 (PDT))

> From: Joel Brobecker <brobecker@adacore.com>
> Date: Sat,  3 Jul 2021 11:48:33 -0700 (PDT)
> 
> Hello,
> 
> I have just finished creating the gdb-11.0.90 pre-release.
> It is available for download at the following location:
> 
>     ftp://sourceware.org/pub/gdb/snapshots/branch/gdb-11.0.90.tar.xz
> 
> A gzip'ed version is also available: gdb-11.0.90.tar.gz.
> 
> Please give it a test if you can and report any problems you might find.

This builds successfully, with minor problems, on native MS-Windows
using mingw.org's MinGW.  The minor problems I found are:

1. A compilation warning in Gnulib's select.c -- reported to the
Gnulib folks.

2. A compilation warning in symtab.c:

       CXX    symtab.o
     symtab.c: In member function 'bool info_sources_filter::matches(const char*) const':
     symtab.c:4247:28: warning: 'to_match' may be used uninitialized in this function [-Wmaybe-uninitialized]
      4247 |       if (m_c_regexp->exec (to_match, 0, NULL, 0) != 0)
	   |           ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~

I guess we need a 'default:' case there?  Or maybe initialize
'to_match' with some suitable value?

Thanks.


  reply	other threads:[~2021-07-08 16:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03 18:48 Joel Brobecker
2021-07-08 16:39 ` Eli Zaretskii via Gdb-patches [this message]
2021-07-08 16:56   ` Simon Marchi via Gdb-patches
2021-07-08 19:03     ` Eli Zaretskii via Gdb-patches
2021-07-11 14:01     ` Joel Brobecker

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=83zguwdajv.fsf@gnu.org \
    --to=gdb-patches@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    /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