May 10, 2020 [Issue 20817] New: parseJSON() generates errors relating to uninitialised values | ||||
|---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=20817 Issue ID: 20817 Summary: parseJSON() generates errors relating to uninitialised values Product: D Version: D2 Hardware: x86 OS: Linux Status: NEW Severity: major Priority: P1 Component: dmd Assignee: nobody@puremagic.com Reporter: alex.braunegg@gmail.com Created attachment 1784 --> https://issues.dlang.org/attachment.cgi?id=1784&action=edit reproducer Background: =========== * Trying to determine if a memory leak exists in trying to diagnose https://github.com/abraunegg/onedrive/issues/893 * Valgrind is showing some interesting data re uninitialised values and possibly lost blocks Valgrind errors: ================ * Use of uninitialised value of size X * Conditional jump or move depends on uninitialised value(s) * Uninitialised value was created by a stack allocation Files Attached: =============== * main.d (reproducer) * valgrind-out-202005101049.txt (valgrind output) * make_with_dmd.sh (compile & test with valgrind) Questions: ========== Is this a valid bug? I have looked through json.d and to me, everything looks like it gets initialised correctly. -- | ||||
Copyright © 1999-2021 by the D Language Foundation
Permalink
Reply