Dear All, I am looking to fix dangling pointer issue and was pleasantly surprised to find the `who-points-at` functionality in valgrind which tells the stack variable names (assuming --read-var-info=yes) and any addresses on heap with holding the searched address. [link]( https://valgrind.org/docs/manual/mc-manual.html#mc-manual.monitor-commands)
The tool is just splendid but I wish there was some way to do it recursively on the heap addresses (i.e who-points-at on the output of previous who-points-at) until we get the stack variable names holding the dangling pointers; something like how core-analyzer's `ref` command does. [link](https://core-analyzer.sourceforge.net/index_files/Page600.html). On a side note, is there a way to know which variable/type a heap address points to? That will be helpful too. Thanks and have a good day! best, Abhi
_______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
