Summary: | Valgrind does not attach to GDB correctly, traceback spits garbage | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | jonesy <soccerdawg> |
Component: | memcheck | Assignee: | Julian Seward <jseward> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | normal | CC: | florian, njn |
Priority: | NOR | ||
Version: | 3.3.1 | ||
Target Milestone: | wanted3.6.0 | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
jonesy
2008-07-22 14:35:41 UTC
Here is a simple test program that will cause this behavior on a default Ubuntu 7.10 system: #include <iostream> struct A { A() { } int i; int j; }; void printA(A* p_a) { std::cout << p_a->i << std::endl; } int main() { A* a = new A(); printA(a); return 0; } We often have GDB attaching problems, it would be good to improve this situation, or at least document better the limitations. The --db-attach feature is deprecated as of valgrind 3.10.0. It will be removed in the next valgrind feature release. The built-in GDB server capabilities are superior and should be used instead. Therefore, this bug will not be fixed. |