From nobody Wed Nov 27 07:34:38 2024 X-Original-To: ports-bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Xyrmv0vF8z5fkS4 for ; Wed, 27 Nov 2024 07:34:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xyrmt6DV3z4hQ1 for ; Wed, 27 Nov 2024 07:34:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1732692878; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=KULpl/8olsQFwlOjRPpMvAdGJJZlihaAN1Lz+Pnu0Wo=; b=v0F4ID9LRSzBisNUjIxWUrdCTY7+QacjQt4bM+8GYrq/laP6qLwfmAT/SVq1SGc5zdVM91 ies4sKf1ibA9jIIdafL9qFJJE8SmV4bcnwSbQR2gyQRwkn79Npk/Guq5fuEnkxjLtYofky OKttZD2xufNptNprHZuUAIsqCLMhxVNNnNwOEI5auE1yzY9ZvjK81cw2XK3ohBWdGjKNOw 1FbyeTFndyGBUyAx2cOUCQXphoy51EvlrYAT+Pj2V8x/AySTR7EakyCSOpw+OvqhYLNqsI SRgzqRzMx3qaqBT9u1CLCW0k5CYt6NvGpjuKqDMPze/Vwn3TqxFkjWOK2Simuw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1732692878; a=rsa-sha256; cv=none; b=bC49HW9PzZ2LqA1RGd/5lp/vSDRhJRWcvAtfQIRYYvdovUQdtZTm4GLKNk/Zj/9hI3USrC D122jpWghT09Mnk03tKsfMNL8UDwKFiw/IDI7Y75xiwjVjNYyC4F1fcUKqMTS3iSPCGuVd VtPSOxpXYs+v09HDqsIgLA/eVURhlR+OM1oQ+FeqFYQk9CTfREsgYEG29Yt9ij9xOKfg1/ B9koNR/KWaOfsZecOdfg67bIaBPtNUHRYeZeE55YCGwEPliOaFag5W0u69DDJYdHKLbGbu h+ZY6SabP1DUrCPEOPDr0qDKibHPDnYZKtIa9DWw1fIJPUnXgkjmKbcH0y5pTA== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Xyrmt5ZPmz1198 for ; Wed, 27 Nov 2024 07:34:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 4AR7Ycmk051180 for ; Wed, 27 Nov 2024 07:34:38 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 4AR7YcNb051179 for ports-bugs@FreeBSD.org; Wed, 27 Nov 2024 07:34:38 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 282998] Qt Creator: Valgrind integration not working Date: Wed, 27 Nov 2024 07:34:38 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: pjfloyd@wanadoo.fr X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Ports bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-ports-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-ports-bugs@freebsd.org Sender: owner-freebsd-ports-bugs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D282998 Bug ID: 282998 Summary: Qt Creator: Valgrind integration not working Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: pjfloyd@wanadoo.fr Bit of background. I use Qt Creator for Valgrind development (and maintain = the FreeBSD port). However I almost never use Valgrind in Creator. I'm working on a Valgrind Bugzilla item that will change Valgrind's XML out= put and I want to check that it does not impact GUIs like CLion and Qt Creator. However it seems as though nothing is working even without any changes to Valgrind. I'm using this small example which has one Conditional jump and one leak. #include using namespace std; int main() { int* pi =3D new int[10]; if (pi[0]) return 1; return 0; } In a terminal I get =3D=3D68245=3D=3D Conditional jump or move depends on uninitialised value(s) =3D=3D68245=3D=3D at 0x400631: main (main.cpp:8) =3D=3D68245=3D=3D=20 =3D=3D68245=3D=3D=20 =3D=3D68245=3D=3D HEAP SUMMARY: =3D=3D68245=3D=3D in use at exit: 3,120 bytes in 7 blocks =3D=3D68245=3D=3D total heap usage: 8 allocs, 1 frees, 76,848 bytes alloc= ated =3D=3D68245=3D=3D=20 =3D=3D68245=3D=3D 40 bytes in 1 blocks are definitely lost in loss record 1= of 7 =3D=3D68245=3D=3D at 0x484E5C4: operator new[](unsigned long) (vg_replace_malloc.c:743) =3D=3D68245=3D=3D by 0x400624: main (main.cpp:7) In Qt Creator if I run Analyze->Valgrind Memory Analyzer then the bar of the Memcheck window shows "Memory Analyzer Tool finished. 2 issues were found.". That's as expected. However the main widget is empty - there are no lines in Memory Issues / Issue | Location. In Application Output I see 08:23:07: valgrind --child-silent-after-fork=3Dyes --xml-socket=3D127.0.0.1= :16219 --log-socket=3D127.0.0.1:64635 --xml=3Dyes --smc-check=3Dstack --tool=3Dmem= check --gen-suppressions=3Dall --track-origins=3Dyes --leak-check=3Dsummary --num-callers=3D25 /home/paulf/scratch/errs/build/clang-Debug/errs If I run Analyze->Valgrind Memory Analyzer with GDB then it works OK if I switch the project to use GDB. It hangs if the default lldb is used - would= it be possible to issue a warning if the user is trying to to this? Or is that something that should be done upstream? I've tried with both the valgrind and valgrind-devel ports. I'm using FreeB= SD 14.1 amd64. I'll try the same example on Linux to see if that works. --=20 You are receiving this mail because: You are the assignee for the bug.=