[Bug gdb/23657] Out of bound memory access

keiths at redhat dot com sourceware-bugzilla@sourceware.org
Mon Oct 28 16:59:00 GMT 2019


--- Comment #8 from Keith Seitz <keiths at redhat dot com> ---
(In reply to Tom de Vries from comment #7)
> (In reply to Keith Seitz from comment #6)
> > This should now be fixed.
> Is it?

It does with the attached reproducer with 950b74950f6 (which doesn't
appear recorded here for some reason).

> I can't reproduce the sigsegv before and after the commit, but using
> valgrind I can get a "Invalid read of size 1" before and after the commit.
> AFAIU, the commit just adds a warning, which indeed triggers. But the commit
> doesn't fix the out of bounds memory access.

The bfd patch recorded here does only add a warning. However, my commit
will emit another warning and skip the section entirely. There is no way
for the code reported by this bug to get triggered, i.e., the entire
.debug_str section will not be read.

That invalid read must be another bug -- one I did not know about.

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

More information about the Gdb-prs mailing list