> Emacs infloops when I press the " key at the end of this line (to the right of
> the last '(':
> matching_dbs = commands.getoutput("""cat
> /xxxx/xxxxxx/xxxxx/xxxxxxxxxxxxxxxxx.xxx | grep "^%s" | grep -v xxx""" %
> region).strip().split(
I assume this is using Emacs's own python.el, not python-mode.el, right?
> in the full file:
I cannot reproduce it here, sadly.
> Here is a debugging session that shows it (I Ctrl-C after it infloops,
> then hit next a bunch of times, hoping it helps):
`next' will only show tiny steps taken right after the point where
you stopped. Typically the inf-loop is much larger, so instead of `next',
use `cont' and interrupt it several times. Each time, use `xbacktrace' to
get a Lisp backtrace (or just `bt' if the Lisp backtrace seems useless).
By comparing the backtraces, we can see at which level of the callstack
happens the inf-loop.
`xbacktrace' only works under gdb (and only if you loaded
...emacs/src/.gdbinit which happens automatically if you start gdb from the
...emacs/src/ directory).
> Is there anything I can do to make this report more useful? It doesn't
> happen with emacs -q unfortunately.
Try to trim down your customization to the smallest one with which you can
still reproduce the problem.
Stefan
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
