Human Folly about “debugger”

index

• Is there an immediate window in visual Studio code to run JavaScript (stackoverflow.com):

  in #VSCode you can evaluate JS or #C# in the current scope in the #debugger window (“Debug Console”)

  on 02024-12-09
• (stackoverflow.com):

  #GDB #debugger #reverse-debugging doesn’t yet support AVX2, but recent glibc lets you turn off AVX2 with an environment variable, so you can GLIBC_TUNABLES=glibc.cpu.hwcaps=-AVX2_Usable,-AVX_Fast_Unaligned_Load gdb ...

  on 02021-02-09
• (gist.github.com):

  +HCU’s .gdbinit file with 2000 lines of #GDB #debugger script from 02010: “A user-friendly gdb configuration file”

  on 02021-02-09
• Debugging GDB pretty printers (stackoverflow.com):

  how to invoke the pdb #debugger when scripting #GDB in #Python: python pdb.run('gdb.execute("print $1[0]")'). Also you can start up an #IPython kernel inside GDB with IPython.embed_kernel() (not sure if this works for notebooks) and define a function in .gdbinit that invokes Python by saying define functionname ... end with a python ... end block inside it.

  on 02021-02-03
• GDB (shanekirk.com):

  oh I didn’t know about the #GDB ptype #debugger command to print struct definitions and stuff. or the tty command to move the program being debugged to a different window so it doesn’t stomp on the TUI

  on 02021-02-03
• GDB tips and tricks 4 reverse debugging (shanekirk.com):

  by default the #GDB #debugger’s record-replay backward stepping has a buffer limit of only 200000 instructions. #reverse-debugging

  on 02021-02-03
• (arxiv.org):

  #rr #debugger #paper from roc et al., 02017 #toread. Reports slowdowns of 1.5× to 8× from recording different kinds of processes. #reverse-debugging

  on 02021-02-03
• Rr (github.com):

  Mozilla #rr supports record-replay backward stepping on fewer platforms than the #GDB #debugger (only amd64 and then only sometimes). But it supports recording the traces to disk. Also, apparently, it requires /proc/sys/kernel/perf_event_paranoid to be no more than 1 for its fast (non -n) mode (like #perf), and doesn’t work inside Docker on the Kudu server, but does work inside KVM. #reverse-debugging

  on 02021-02-03
• Reverse execution (sourceware.org):

  #documentation for the #GDB #debugger’s record-replay backward stepping #reverse-debugging

  on 02021-02-03
• (stackoverflow.com):

  Mozilla #rr, which supports the #GDB #debugger, is reputed to be better than GDB’s built-in record-replay backward stepping: “more reliable”, “small performance drop”, “generated traces are small”, “supports AVX” #reverse-debugging

  on 02021-02-03
• Debugger (web.archive.org):

  Bil Lewis’s Omniscient #Debugger provided record-replay backward stepping of #Java programs in NetBeans and Eclipse #reverse-debugging

  on 02021-02-03