| Summary: | Valgrind crashes when running KStars test | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Hy <hymur67> |
| Component: | memcheck | Assignee: | Julian Seward <jseward> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | pjfloyd |
| Priority: | NOR | ||
| Version First Reported In: | 3.17.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | this is the stderr/stdout for the crash, which seems to include a stack trace | ||
I don't see any Valgrind errors. There's a guest 'abort()' at the end. All of the test framework noise makes it very hard to read. Can you run the test on its own and attach the Valgrind-only output? You may also need a debug build (or debuginfo) for Qt to see the locations of this part of the stack ==72018== by 0x4885AA1: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Test.so.5.12.8) ==72018== by 0x74759D1: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12.8) Thanks you Paul. I think you are right. I confused the stack-trace output there (which I guess was a kill timeout) with a stack-trace from ValGrind. I'll resolve this, look further, and get back if it turns out there really is an issue. Appreciate your help, Hy |
Created attachment 149910 [details] this is the stderr/stdout for the crash, which seems to include a stack trace SUMMARY When I try to run valgrind to find memory issues in a test for KStars (a KDE planetarium program) I get a crash. I believe I'm using the latest valgrind release for Ubuntu 20.04 The test runs several parallel threads to test thread-safeness of some KStars code. I've attached the output. STEPS TO REPRODUCE 1. You'd need the compiled KStars test, if you'd like to reproduce, let me know and I can help you compile it. 2. 3. OBSERVED RESULT crash EXPECTED RESULT no crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: Just tried on Ubuntu 20.04 ADDITIONAL INFORMATION