On Wed, 2004-11-24 at 15:23 -0600, Ben Wing wrote:
> #1: Failed with "Wrong type argument: integerp, append"
> #2: Failed with "Invalid function: 1"
> #3: Failed with "Symbol's value as variable is void:
> compilation-old-error-list"
> #4: Failed with "Wrong type argument: integer-or-char-p, t"
> #5: Crash, see attached bt.txt.
> #6: Success!
>
> I would appreciate if someone could have a look at this. Let
> me know if you need more info and I'll try to provide.
Yuck. Your backtrace is clear but unfortunately these bytecode problems are
hard to diagnose.
What would help is
[1] Before opening the file the first time, put a breakpoint at signal_1().
[2] When you get the first failure, get both a C and lisp backtrace and send
them. You can get a Lisp backtrace by calling debug_backtrace().
Sorry about the silence; I've recently upgraded to Fedora Core 3, and
haven't seen any crashes or weird behaviour yet (*knocks wood*). I'll
keep an eye on things, and will get back to you if I manage to reproduce
the problems and upgrade my gdb skills to produce what you requested
above.