[Bug debug/88742] New: Debugger jumps back when stepping over class destructor

2019-01-07 Thread ks1322 at gmail dot com
Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: ks1322 at gmail dot com Target Milestone: --- This is basically the same bug report as the Bug 49951 because it can be reproduced with recent version of gcc. I don't know whether Bug

[Bug libstdc++/109064] New: Maximum recursion depth exceeded in std::shared_ptr xmethod

2023-03-08 Thread ks1322 at gmail dot com via Gcc-bugs
Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: ks1322 at gmail dot com Target Milestone: --- Based on https://stackoverflow.com/questions/75652764/gdb-fails-with-python-exception-class-recursionerror-maximum-recursion-dep Seems

[Bug libstdc++/109064] Maximum recursion depth exceeded in std::shared_ptr xmethod

2023-03-08 Thread ks1322 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109064 --- Comment #1 from ks1322 at gmail dot com --- Looks like infinite recursion is here, SharedPtrUseCountWorker.__init__ calls itself ``` class SharedPtrUseCountWorker(gdb.xmethod.XMethodWorker): "Implements std::shared_ptr::use_

[Bug libstdc++/112491] New: std::deque::size xmethod output is wrong

2023-11-12 Thread ks1322 at gmail dot com via Gcc-bugs
: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: ks1322 at gmail dot com Target Milestone: --- For this code: ``` #include int main() { std::deque d; d.push_front(0); return 0; } ``` deque size xmethod produces wrong result ``` $ gdb -batch -ex "b 8