On Mon, Feb 07 2011, Wes Hardaker wrote:

> I'd try and find out where the errors are getting generated from, but
> (setq debug-on-error t) doesn't seem to consider read-only violations as
> errors, so I can't get a stack trace.  Anyone know how to accomplish
> getting a stack trace for read-only errors?

Remove read-only from `debug-ignored-errors'.

-- 
Julien Danjou
❱ http://julien.danjou.info