https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96780
--- Comment #14 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Jason Merrill from comment #10) > It seems the libstdc++ python hooks could set that up for users with > gdb.execute ("skip std::move")? No, that doesn't work. You need to use 'skip "std::move<int&>"' otherwise it doesn't skip it: $ gdb -q -ex start -ex 'skip std::move' -ex step -ex step -ex cont -ex q a.out Reading symbols from a.out... Temporary breakpoint 1 at 0x40110e: file move.C, line 16. Starting program: /tmp/a.out Temporary breakpoint 1, main () at move.C:16 16 int i = 0; Function std::move will be skipped when stepping. 17 return std::move(i); std::move<int&> (__t=@0x7fffffffd77c: 0) at move.C:11 11 { return static_cast<typename std::remove_reference<_Tp>::type&&>(__t); } And std::move* doesn't work either: $ gdb -q -ex start -ex 'skip std::move*' -ex step -ex step -ex cont -ex q a.out Reading symbols from a.out... Temporary breakpoint 1 at 0x40110e: file move.C, line 16. Starting program: /tmp/a.out Temporary breakpoint 1, main () at move.C:16 16 int i = 0; Function std::move* will be skipped when stepping. 17 return std::move(i); std::move<int&> (__t=@0x7fffffffd77c: 0) at move.C:11 11 { return static_cast<typename std::remove_reference<_Tp>::type&&>(__t); }