gud

I'm a big fan of Emacs, and use it a lot, especially while programming and debugging (using gud) (C/C++). Recently I had to debug a program (rather simple but that compute on a lot of data (Graph Theory)), but I had a rather annoying problem. During the execution step by step of the program, I get the following error: error in process filter: Stack overflow in regexp matcher I made some research to find out what it was, and I found out this post: Debugging in emacs (with gud) often results in stack overflow error . So as I understand it, there is a problem with the regexp matcher and the fact

I use GDB in Emacs 24 with gdb-many-windows set to t , usually in its own frame. I like to have a separate editing frame. It looks like this (apologies for my crude ASCII diagram): +-------------+-------------+ | gdb | locals | +-------------+-------------+ | source | I/O | | | | +-------------+-------------+ | stack | breakpoints | +-------------+-------------+ This works pretty well except for one big problem. Whenever gdb needs to display a different source buffer, e.g., after up/down/step, it doesn't always show it in the "source" window. For example, if I have the same buffer open in a

I'm using python.el If I choose 'debugger' from the menu, and enter 'python -m pdb myfile.py', gud starts, and in a split frame I see the (Pdb) prompt in one, and my python code in the other with a caret on the first line, indicating that it's ready to go. For example 'n' steps to the next line and the caret moves accordingly. If instead I enter 'python -m ipdb myfile.py', the frame splits, and one split is labeled gud, but there's no ipdb console evident. In other words, this way of starting ipdb doesn't seem to work. Ipdb works just fine if I manually insert a breakpoint into my python code