public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/31150] [gdb/build] m_uiout may be used uninitialized in this function [-Wmaybe-uninitialized]
Date: Mon, 25 Dec 2023 11:50:06 +0000	[thread overview]
Message-ID: <bug-31150-4717-YL4cy1dvJw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31150-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31150

--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #3)
> Which compiler is this?
> I think this was https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80635

That particular PR is fixed in gcc 11.1, and this is with gcc 11.4 on ubuntu
22.04.

Anyway, this fixes it as well:
...
diff --git a/gdb/ui-out.h b/gdb/ui-out.h
index 07567a1df35..ce3bc86b651 100644
--- a/gdb/ui-out.h
+++ b/gdb/ui-out.h
@@ -406,7 +406,10 @@ class ui_out_emit_type

   ~ui_out_emit_type ()
   {
+    DIAGNOSTIC_PUSH
+    DIAGNOSTIC_IGNORE ("-Wmaybe-uninitialized")
     m_uiout->end (Type);
+    DIAGNOSTIC_POP
   }

   DISABLE_COPY_AND_ASSIGN (ui_out_emit_type);
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-12-25 11:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 15:56 [Bug build/31150] New: " vries at gcc dot gnu.org
2023-12-24  9:24 ` [Bug build/31150] " vries at gcc dot gnu.org
2023-12-24  9:33 ` vries at gcc dot gnu.org
2023-12-24 17:51 ` tromey at sourceware dot org
2023-12-25 11:50 ` vries at gcc dot gnu.org [this message]
2023-12-25 17:42 ` tromey at sourceware dot org
2024-01-04 12:03 ` vries at gcc dot gnu.org
2024-01-04 12:04 ` vries at gcc dot gnu.org
2024-01-05 10:23 ` ssbssa at sourceware dot org

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=bug-31150-4717-YL4cy1dvJw@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).