From: Eli Zaretskii <eliz@gnu.org>
To: brobecker@adacore.com
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 8.1.90 available for testing
Date: Sun, 29 Jul 2018 02:37:00 -0000 [thread overview]
Message-ID: <837eleu5q7.fsf@gnu.org> (raw)
In-Reply-To: <83y3e834jw.fsf@gnu.org> (message from Eli Zaretskii on Wed, 18 Jul 2018 19:13:39 +0300)
Ping! Should anything be done about the last warning I describe
below?
> Date: Wed, 18 Jul 2018 19:13:39 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> CC: gdb-patches@sourceware.org
>
> > From: Joel Brobecker <brobecker@adacore.com>
> > Date: Wed, 4 Jul 2018 09:22:02 -0700 (PDT)
> >
> > I have just finished creating the gdb-8.1.90 pre-release.
> > It is available for download at the following location:
> >
> > ftp://sourceware.org/pub/gdb/snapshots/branch/gdb-8.1.90.tar.xz
> >
> > A gzip'ed version is also available: gdb-8.1.90.tar.gz.
> >
> > Please give it a test if you can and report any problems you might find.
>
> I've built this with mingw.org's MinGW. I found one problem in
> libiberty (which I will report separately), and I saw 3 warnings while
> compiling GDB sources:
>
> CXX infrun.o
> In file included from infrun.c:26:0:
> inferior.h: In function 'void handle_vfork_child_exec_or_exit(int)':
> inferior.h:533:39: warning: '*((void*)(& maybe_restore_inferior)+20).scoped_restore_current_inferior::m_saved_inf' may be used uninitialized in this function [-Wmaybe-uninitialized]
> { set_current_inferior (m_saved_inf); }
> ^
> infrun.c:929:6: note: '*((void*)(& maybe_restore_inferior)+20).scoped_restore_current_inferior::m_saved_inf' was declared here
> maybe_restore_inferior;
> ^~~~~~~~~~~~~~~~~~~~~~
> In file included from inferior.h:49:0,
> from infrun.c:26:
> progspace.h:285:47: warning: '*((void*)(& maybe_restore_inferior)+16).scoped_restore_current_program_space::m_saved_pspace' may be used uninitialized in this function [-Wmaybe-uninitialized]
> { set_current_program_space (m_saved_pspace); }
> ^
> infrun.c:929:6: note: '*((void*)(& maybe_restore_inferior)+16).scoped_restore_current_program_space::m_saved_pspace' was declared here
> maybe_restore_inferior;
> ^~~~~~~~~~~~~~~~~~~~~~
>
> Same warnings were in GDB 8.1; ignored.
>
> CXX symfile.o
> symfile.c: In function 'void set_objfile_default_section_offset(objfile*, const section_addr_info&, CORE_ADDR)':
> symfile.c:2114:14: warning: types may not be defined in a for-range-declaration
> for (const struct other_sections *objf_sect : objf_addrs_sorted)
> ^~~~~~
>
> The first two I saw in GDB 8.1 and reported back in January. I
> believe the conclusion was that we disregard these warnings?
>
> But what about the 3rd one?
next prev parent reply other threads:[~2018-07-29 2:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 16:32 Joel Brobecker
2018-07-18 16:13 ` Eli Zaretskii
2018-07-19 14:37 ` Tom Tromey
2018-07-19 14:48 ` Eli Zaretskii
2018-07-29 2:37 ` Eli Zaretskii [this message]
2018-07-29 18:43 ` Tom Tromey
2018-07-31 16:58 ` Eli Zaretskii
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=837eleu5q7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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