This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [ANNOUNCEMENT] GDB 8.1 release branch created!
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Sergio Durigan Junior <sergiodj at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 17 Jan 2018 05:36:31 +0200
- Subject: Re: [ANNOUNCEMENT] GDB 8.1 release branch created!
- Authentication-results: sourceware.org; auth=none
- References: <announce.20180105041805.3FC35808E9@joel.gnat.com> <83h8rlyakm.fsf@gnu.org> <87po69zkxe.fsf@redhat.com> <87po69y20p.fsf@redhat.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Sergio Durigan Junior <sergiodj@redhat.com>
> Cc: gdb-patches@sourceware.org
> Date: Tue, 16 Jan 2018 15:36:22 -0500
>
> I'm not sure why this one is happening. I think it has something to do
> with the fact that we're declaring "maybe_restore_inferior" as
> gdb::optional, because scoped_restore_current_inferior's constructor
> already takes care of initializing "m_saved_inf" (same goes for
> scoped_restore_current_program_space).
>
> If that is the case, then maybe we can mark the "uninitialized variable"
> warning for "m_saved_inf" and "m_saved_pspace".
Sorry, I'm not sure I understand what does your suggestion here mean
in practice. Can you elaborate, or show a proposed patch?
Thanks.