Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 08 Jul 2016 13:26:32 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 210798] devel/gdb: Uninitialized variables found presenting possible security issues or bugs
Message-ID:  <bug-210798-13-Kl1C49BM2l@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-210798-13@https.bugs.freebsd.org/bugzilla/>
References:  <bug-210798-13@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210798

luca.pizzamiglio@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|maintainer-feedback?(luca.p |maintainer-feedback+
                   |izzamiglio@gmail.com)       |

--- Comment #5 from luca.pizzamiglio@gmail.com ---
Hi Mark,

thanks to report those problems.
Some comments:

gdb/rs6000-tdep.c: is already fixed in the upstream, so I can merge it back
soon

gdb/compile/compile-loc2c.c: initializing uoffset to zero would silent the
warning, but I'm not sure if it's correct; I guess that the correct behavio=
r is
granted by well formed dwarf expressions.

gdb/xcoffread.c: a solution here is hard to find; the uninitialized path sh=
ould
happen only with malformed xcoff, so read_xcoff_symtab() run without issues
with well formed xcoff.

Soon I'll provide a patch to fix the first two warnings; the last one requi=
re a
feedback from gdb's people.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-210798-13-Kl1C49BM2l>