Mailinglist Archive: opensuse-factory (536 mails)

< Previous Next >
Re: [opensuse-factory] Leap 15 - valgrind misreports the number of allocations and amount of memory allocated
On 05/05/2018 07:51 PM, Stefan Brüns wrote:
On Sonntag, 6. Mai 2018 01:56:14 CEST David C. Rankin wrote:
All,

I have filed https://bugzilla.opensuse.org/show_bug.cgi?id=1092054 against
valgrind misreporting the number of allocations, and size of memory
allocated. valgrind has correctly reported in all prior openSuSE releases,
but not reports additional allocations (which gets exponentially worse as
the number of allocations in your code increases)

The valgrind report is completely correct.

Regards,

Stefan


If it is reporting 1028 bytes allocated for 1-integer, it is most certainly
NOT correct.

Are you saying it was incorrect in all prior releases reporing 4-bytes per-int
instead of 1028-bytes per-int?

The two reportings from Leap 42.3 and Leap 15 are completely different --
which one are you saying is right? It's a binary, mutually exclusive
proposition...

I note you cite no reference and no prior comparison in making your assertion
that the valgrind output in Leap 15 is correct.

What the problem points to is a missing or wrong exclusion file for gcc 7.3.
Ignoring the problem, or just saying "it's correct", won't fix it.

--
David C. Rankin, J.D.,P.E.

< Previous Next >
Follow Ups