[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Blocking call to accept-process-output with quit inhibited!! [11 tim
From: |
Stefan Monnier |
Subject: |
Re: Blocking call to accept-process-output with quit inhibited!! [11 times] |
Date: |
Thu, 09 Sep 2010 00:54:40 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
>>> Well... `error' is a Lisp function, so I can't really call it from
>>> there?
>> error is also a C function, see eval.c.
> Right. I'm still not getting any backtraces, though.
Sometimes the debugger is disabled because we're in the middle of
a special situation (e.g. during redisplay). So maybe that's
the problem.
You may want to place a C breakpoint on the `message' (aka `error') call
and use xbacktrace from GDB when you hit it. It's not as
convenient, tho.
Stefan
Re: Blocking call to accept-process-output with quit inhibited!! [11 times], Lars Magne Ingebrigtsen, 2010/09/07
- Re: Blocking call to accept-process-output with quit inhibited!! [11 times], Stefan Monnier, 2010/09/08
- Re: Blocking call to accept-process-output with quit inhibited!! [11 times], Lars Magne Ingebrigtsen, 2010/09/08
- Re: Blocking call to accept-process-output with quit inhibited!! [11 times], Andreas Schwab, 2010/09/08
- Re: Blocking call to accept-process-output with quit inhibited!! [11 times], Lars Magne Ingebrigtsen, 2010/09/08
- Re: Blocking call to accept-process-output with quit inhibited!! [11 times],
Stefan Monnier <=
- Re: Blocking call to accept-process-output with quit inhibited!! [11 times], Lars Magne Ingebrigtsen, 2010/09/08
- Re: Blocking call to accept-process-output with quit inhibited!! [11 times], Lars Magne Ingebrigtsen, 2010/09/16
- Re: Blocking call to accept-process-output with quit inhibited!! [11 times], Stefan Monnier, 2010/09/17