| Summary: | Valgrind hangs when about to exit | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Opera Wang <opera.wang+kde> |
| Component: | memcheck | Assignee: | Julian Seward <jseward> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 3.13.0 | ||
| Target Milestone: | --- | ||
| Platform: | PCLinuxOS | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
mem check hangs by mutex lock
mem check hangs at glibc? |
||
Created attachment 113336 [details]
mem check hangs at glibc?
Statistically speaking, this is most likely to be a (locking) bug in your program. You run it with --tool=helgrind to get more information. Closing as invalid. If you have more information that suggests it's really a bug in Valgrind -- including a small test case -- then please feel free to reopen. |
Created attachment 113335 [details] mem check hangs by mutex lock We're using Valgrind 3.13 to check memory leak issues, and some test cases randomly hangs when it exit We do see 2 kind of hangs, the 1st one seems happen more frequently, and hangs @ pthread_mutex_lock, the 2nd one hangs @ tls_get_addr_tail, please see attached file