Bug#669416: ltrace does not report virtual methods from heap-allocated objects

2024-11-29 Thread наб
Control: found -1 0.7.91~git20230705.8eabf68-1 Control: tags -1 + upstream wontfix Yes. If we reduce f.cpp to #include "foo.hpp" int main() { foo* f = new foo_child; // ltrace doesn't report this one? f->virtual_foo(); f->pure_virtual_foo(); } then $ nm -C f | grep

Bug#669416: ltrace does not report virtual methods from heap-allocated objects

2012-04-19 Thread Chip Christian
Package: ltrace Version:0.6.0 using g++ 4.4.6, ltrace 0.6.0 and earlier I built a shared library from foo.cpp and linked it to a program built from f.cpp. All method names are reported for an auto, but if I call operator new, the virtual (pure or otherwise) never show up: $ ltrace -C ./f (0, 0,