> > 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 ;-)
It's on my todo-list. 8-) > > 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. The sysadmin says that they applied official patches and some "manual bugfixes". The definitions of uint16_t (I supplied that manually) and sockaddr_in6 are missing. I will investigate this further. Additionally, I tested emacs on an updated system running Digital Unix V5.1A and it compiled flawlessly with the native cc. IPv6 _and_ dumping were fine! > > (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? No, they don't. 8-( _______________________________________________ emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
