-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "James" == James LewisMoss <email@example.com> writes:
>>>>> On Fri, 27 Jul 2001 13:05:44 -0700, Jim McCloskey <firstname.lastname@example.org> said:
Jim> Does anyone know how I might trace this problem to its origins? Or
Jim> solve it? Thanks very much in advance,
James> Likely setting the var debug-on-error to t will give you a
James> backtrace (I'm xemacs guy and it works there).
Or you can do "M-x toggle-debug-on-error".
Unfortunately, now every error will generate a backtrace. I don't think
there's any way to get a trace after the fact, so it's best if you can
figure out something that causes that error, turn on debug-on-error, and
get the backtrace.
Hubert Chan <email@example.com> - http://www.geocities.com/hubertchan/
PGP/GnuPG key: 1024D/651854DF71FDA37F
Fingerprint: 6CC5 822D 2E55 494C 81DD 6F2C 6518 54DF 71FD A37F
Key available at wwwkeys.pgp.net. Please encrypt *all* e-mail to me.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
-----END PGP SIGNATURE-----