https://sourceware.org/bugzilla/show_bug.cgi?id=28685
--- Comment #10 from Evgeny Vereshchagin ---
Looks like the memory leak is gone. Thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
[v3]
The test handles infinite loops much better now.
In https://sourceware.org/bugzilla/show_bug.cgi?id=28715#c4 it took
it about 5 hours on Packit to discover an infinite loop on 32 bit
platforms because it didn't enforce any timeouts. It was fixed
by passing --tmout_sigvtalrm to honggfuzz (whic
https://sourceware.org/bugzilla/show_bug.cgi?id=28685
--- Comment #9 from Mark Wielaard ---
(In reply to Evgeny Vereshchagin from comment #7)
> Created attachment 13869 [details]
> archive with a report and a file triggering a memory leak
>
> Thanks! That branch helped me a lot. I rebased it on
There was a small memory leak if an error was detected in some places
in dwfl_segment_report_module after the build_id.memory was alredy
allocated. Fix this by moving initialization of struct elf_build_id
early and always free the memory, if not NULL, at exit.
https://sourceware.org/bugzilla/show_
https://sourceware.org/bugzilla/show_bug.cgi?id=28708
--- Comment #10 from Evgeny Vereshchagin ---
(In reply to Mark Wielaard from comment #9)
> (In reply to Evgeny Vereshchagin from comment #7)
> > > Note that packit doesn't use real hardware for various architectures but
> > > "container emulat
https://sourceware.org/bugzilla/show_bug.cgi?id=28685
--- Comment #8 from Evgeny Vereshchagin ---
I can't reproduce that "unknown-crash on address 0x7f54aacd7000" anymore.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=28715
--- Comment #8 from Evgeny Vereshchagin ---
(In reply to Mark Wielaard from comment #7)
> (In reply to Evgeny Vereshchagin from comment #2)
> > There seem to be quite a few new patches on the mailing list. I wonder if
> > it's possible to some
https://sourceware.org/bugzilla/show_bug.cgi?id=28710
--- Comment #2 from Evgeny Vereshchagin ---
With https://code.wildebeest.org/git/user/mjw/elfutils/log/?h=fuzz rebased on
top of my "fuzzing" branch I can no longer reproduce this issue. Thanks!
--
You are receiving this mail because:
You ar
https://sourceware.org/bugzilla/show_bug.cgi?id=28685
--- Comment #7 from Evgeny Vereshchagin ---
Created attachment 13869
--> https://sourceware.org/bugzilla/attachment.cgi?id=13869&action=edit
archive with a report and a file triggering a memory leak
Thanks! That branch helped me a lot. I re
https://sourceware.org/bugzilla/show_bug.cgi?id=28715
--- Comment #7 from Mark Wielaard ---
(In reply to Evgeny Vereshchagin from comment #2)
> There seem to be quite a few new patches on the mailing list. I wonder if
> it's possible to somehow fetch a branch with all of them so that I could
> ju
https://sourceware.org/bugzilla/show_bug.cgi?id=28685
--- Comment #6 from Mark Wielaard ---
I cannot replicate this with either an amd64 build or a i686 build.
I might have some more patches applied locally because the line
dwfl_segment_report_module.c:466 doesn't contain a memcpy call for me.
A
https://sourceware.org/bugzilla/show_bug.cgi?id=28715
--- Comment #6 from Mark Wielaard ---
(In reply to Evgeny Vereshchagin from comment #5)
> I can't seem to apply that patch:
It might be easier to pick up the whole "fuzz" branch from my tree:
https://code.wildebeest.org/git/user/mjw/elfutils/
https://sourceware.org/bugzilla/show_bug.cgi?id=28708
--- Comment #9 from Mark Wielaard ---
(In reply to Evgeny Vereshchagin from comment #7)
> > Note that packit doesn't use real hardware for various architectures but
> > "container emulation" which causes various testcases to fail.
> >
> I thi
https://sourceware.org/bugzilla/show_bug.cgi?id=28715
--- Comment #5 from Evgeny Vereshchagin ---
I can't seem to apply that patch:
```
$ git am --exclude=libdwfl/ChangeLog p4.patch
Applying: libdwfl: Rewrite GElf_Nhdr reading in dwfl_segment_report_module
error: patch failed: libdwfl/dwfl_segmen
https://sourceware.org/bugzilla/show_bug.cgi?id=28715
--- Comment #4 from Evgeny Vereshchagin ---
(In reply to Evgeny Vereshchagin from comment #3)
> (In reply to Mark Wielaard from comment #1)
> > I couldn't replicate the infinite loop, which I assume has been fixed by:
> > https://sourceware.or
https://sourceware.org/bugzilla/show_bug.cgi?id=28685
--- Comment #5 from Evgeny Vereshchagin ---
Created attachment 13867
--> https://sourceware.org/bugzilla/attachment.cgi?id=13867&action=edit
regression
I ran the fuzzer a bit longer and it seems
https://sourceware.org/pipermail/elfutils-dev
https://sourceware.org/bugzilla/show_bug.cgi?id=28715
--- Comment #3 from Evgeny Vereshchagin ---
(In reply to Mark Wielaard from comment #1)
> I couldn't replicate the infinite loop, which I assume has been fixed by:
> https://sourceware.org/pipermail/elfutils-devel/2021q4/004557.html
I haven't
https://sourceware.org/bugzilla/show_bug.cgi?id=28685
--- Comment #4 from Evgeny Vereshchagin ---
I can confirm that with those three patches applied I can no longer reproduce
the issue. I tested it with both `--enable-honggfuzz` from
https://sourceware.org/pipermail/elfutils-devel/2021q4/004554.
18 matches
Mail list logo
