[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: problems building on OSF1
From: |
Eli Zaretskii |
Subject: |
Re: problems building on OSF1 |
Date: |
Sat, 11 Nov 2006 11:36:26 +0200 |
> Date: Sat, 11 Nov 2006 01:11:32 +0100
> From: Anselm Helbig <address@hidden>
> Cc: address@hidden,
> Chong Yidong <address@hidden>
>
> Sorry for the delay and for messing up the threading, I'm afraid my
> spamfilter ate your last mail, Eli.
Then perhaps you should be working on your spam filter ;-)
> Maybe I should _really_ talk to our sysadmins...
Yes, please do. I don't want to disable IPv6 for your system if we
aren't sure that the problem is indeed with all such systems, not
specific to your machine.
> (gdb) break Fsignal
> Breakpoint 2 at 0x1201c7cbc: file eval.c, line 1622.
> (gdb) run -batch -l loadup dump
> Starting program:
> /amd/molgix/4/home/abt_lh/helbig/compile/tru64/emacs-22.0.90/src/temacs
> -batch -l loadup dump
> Loading loadup.el (source)...
> Using load-path (/home/helbig/compile/tru64/emacs-22.0.90/lisp)
> Loading emacs-lisp/byte-run...
> Loading emacs-lisp/backquote...
> Loading subr...
> Symbol's value as variable is void: nil
>
> Program exited with code 0377.
> You can't do that without a process to debug.
> (gdb)
How about if you put breakpoints in both `message' and `message3',
does any of them break? If so, what do you see in the C and Lips
backtraces (the "bt" and "xbacktrace" commands)?