Date: Wed, 27 Nov 2024 07:34:38 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 282998] Qt Creator: Valgrind integration not working Message-ID: <bug-282998-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
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 <iostream> 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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-282998-7788>