Re: rzadki bład w programie w C++ - Grupy dyskusyjne w eGospodarka.pl

eGospodarka.pl › Grupy › pl.comp.programming › rzadki bład w programie w C++ › Re: rzadki bład w programie w C++

X-Received: by 2002:ac8:6bcc:: with SMTP id b12mr4762938qtt.243.1630006374170; Thu,
26 Aug 2021 12:32:54 -0700 (PDT)
X-Received: by 2002:ac8:6bcc:: with SMTP id b12mr4762938qtt.243.1630006374170; Thu,
26 Aug 2021 12:32:54 -0700 (PDT)
Path: news-archive.icm.edu.pl!news.icm.edu.pl!newsfeed.pionier.net.pl!3.eu.feeder.erj
e.net!feeder.erje.net!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2
.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnew
s.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: pl.comp.programming
Date: Thu, 26 Aug 2021 12:32:54 -0700 (PDT)
In-Reply-To: <sg8o4g$1jc$1@dont-email.me>
Injection-Info: google-groups.googlegroups.com;
posting-host=2a00:f41:80de:e9bd:c5be:eaaf:5c5e:5517;
posting-account=RisGjQoAAABn52Xt4Qe_spC4J60eD_kY
NNTP-Posting-Host: 2a00:f41:80de:e9bd:c5be:eaaf:5c5e:5517
References: <9...@g...com>
<4...@g...com>
<2...@g...com>
<c...@g...com>
<3...@g...com>
<f...@g...com>
<4...@g...com>
<2...@g...com>
<5...@g...com>
<c...@g...com>
<a...@g...com>
<9...@g...com>
<b...@g...com>
<1...@g...com>
<a...@g...com>
<sg8o4g$1jc$1@dont-email.me>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <c...@g...com>
Subject: Re: rzadki bład w programie w C++
From: Robert Magdziarz <r...@r...e-kei.pl>
Injection-Date: Thu, 26 Aug 2021 19:32:54 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: news-archive.icm.edu.pl pl.comp.programming:215618
[ ukryj nagłówki ]
czwartek, 26 sierpnia 2021 o 20:56:17 UTC+2 heby napisał(a):
> On 26/08/2021 19:29, Robert Magdziarz wrote:
> > Mój program dla tych samych danych wejściowych (tego samego kodu PHP) zachowuje
się poprawnie, a czasami (ów rzadki przypadek) niepoprawnie.
> Sprawdziłeś już valgrinda? Isnieje wysokie prawdopodobieństwo, że da
> prawidłową odpowiedź na to pytanie.

Nie bardzo go rozumiem:

==4215==
==4215== HEAP SUMMARY:
==4215== in use at exit: 238,583 bytes in 1,676 blocks
==4215== total heap usage: 29,427,297 allocs, 29,425,621 frees, 391,059,828 bytes
allocated
==4215==
==4215== LEAK SUMMARY:
==4215== definitely lost: 0 bytes in 0 blocks
==4215== indirectly lost: 0 bytes in 0 blocks
==4215== possibly lost: 0 bytes in 0 blocks
==4215== still reachable: 238,583 bytes in 1,676 blocks
==4215== of which reachable via heuristic:
==4215== newarray : 1,408 bytes in 11 blocks
==4215== suppressed: 0 bytes in 0 blocks
==4215== Rerun with --leak-check=full to see details of leaked memory
==4215==
==4215== For counts of detected and suppressed errors, rerun with: -v
==4215== Use --track-origins=yes to see where uninitialised values come from
==4215== ERROR SUMMARY: 8864 errors from 8 contexts (suppressed: 0 from 0)