w3 dies in make-charset for 'w3-dingbats'
23 years, 12 months
Steve Harris
Steve Harris
This bug report will be sent to the XEmacs Development Team,
not to your local site managers!!
Please write in English, because the XEmacs maintainers do not have
translators to read other languages for them.
In XEmacs 21.2 (beta31) "Iris" [Lucid] (sparc-sun-solaris2.5.1, Mule) of Mon Mar 20 2000 on zhora
configured using `configure --site-includes=/usr/local/include --site-libraries=/usr/local/sun4/lib --prefix=/tools/xemacs-beta/21.2-pdump --with-sound=none --with-mule --debug=no --error-checking=none --without-tooltalk --without-workshop --pdump'
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
If I start up XEmacs and invoke W3 ('M-x w3'), XEmacs crashes almost
immediately. Gnus also invokes w3 when it encounters an HTML message,
which produces the exact same crashing behavior. It doesn't seem to
matter whether I do any other activities before invoking w3, with one
exception. If I specify w3 on the xemacs command-line ('-f w3'), it
starts up and prints the error
"No more character sets for this dimension: 1"
and otherwise works okay. If I then invoke w3 again ('M-x w3'), the
same crash behavior occurs.
I first noticed this behavior as of Thursday, 23 March, 2000.
Lisp backtrace follows:
make-charset(w3-dingbats "Dingbats character set for Emacs/W3" (registry "" dimension 1 chars 96 final ?:))
byte-code("..." [mule-sysdep-version xemacs find-charset w3-dingbats make-charset "Dingbats character set for Emacs/W3" (registry "" dimension 1 chars 96 final ?:) (4.0 3.0 3.1) charsetp define-charset nil vector 1 96 ?: 0 "dingbats" "emacs/w3-dingbats"] 13)
# bind (current-load-list)
# (unwind-protect ...)
# bind (load-file-name)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
load-internal("w3-display" nil t nil binary)
# bind (path handler filename nosuffix nomessage noerror file)
load("w3-display" nil t nil)
# (unwind-protect ...)
require(w3-display)
byte-code("..." [fboundp w3 autoload load-path p name file-exists-p expand-file-name "w3-vars.elc" file-name-directory name2 p2 directory-file-name require w3-sysdp w3-cfg mule-sysdp widget featurep efs efs-auto nil (byte-code "ÀÁ!" [require ange-ftp] 2) ((error)) cl css url-vars url-parse w3-vars w3-display] 7)
# bind (current-load-list)
# (unwind-protect ...)
# bind (load-file-name)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
# (unwind-protect ...)
load-internal("w3" nil nil nil binary)
# bind (path handler filename nosuffix nomessage noerror file)
load("w3" nil nil nil)
# (unwind-protect ...)
command-execute(w3 t)
# bind (_execute_command_keys_ _execute_command_name_ prefix-arg)
execute-extended-command(nil)
# bind (command-debug-status)
call-interactively(execute-extended-command)
# (condition-case ... . error)
# (catch top-level ...)
Core file backtrace follows:
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "sparc-sun-solaris2.5.1"...
warning: core file may not match specified executable file.
Core was generated by `/users/lipp/xemacs-beta/21.2-pdump/bin/xemacs -f w3'.
Program terminated with signal 11, Segmentation Fault.
Reading symbols from /usr/lib/libXm.so.3...done.
Reading symbols from /usr/openwin/lib/libtiff.so...done.
Reading symbols from /usr/local/sun4/lib/libpng.so.2...done.
Reading symbols from /usr/local/sun4/lib/libjpeg.so.62...done.
Reading symbols from /usr/local/sun4/lib/libz.so.1.1.3...done.
Reading symbols from /usr/openwin/lib/libXpm.so.4.10...done.
Reading symbols from /usr/lib/libXmu.so.4...done.
Reading symbols from /usr/lib/libXt.so.4...done.
Reading symbols from /usr/lib/libXext.so.0...done.
Reading symbols from /usr/lib/libX11.so.4...done.
Reading symbols from /usr/lib/libdl.so.1...done.
Reading symbols from /usr/lib/libkvm.so.1...done.
Reading symbols from /usr/lib/libkstat.so.1...done.
Reading symbols from /usr/lib/libintl.so.1...
warning: Lowest section in /usr/lib/libintl.so.1 is .dynamic at 0x74
done.
Reading symbols from /usr/lib/libm.so.1...done.
Reading symbols from /usr/lib/libsocket.so.1...done.
Reading symbols from /usr/lib/libnsl.so.1...done.
Reading symbols from /usr/lib/libelf.so.1...done.
Reading symbols from /usr/lib/libc.so.1...done.
Reading symbols from /usr/lib/libSM.so.6...done.
Reading symbols from /usr/lib/libICE.so.6...done.
Reading symbols from /usr/lib/libmp.so.2...done.
Reading symbols from /usr/platform/SUNW,Ultra-4/lib/libc_psr.so.1...done.
#0 0xef188244 in _libc_kill () from /usr/lib/libc.so.1
(gdb) where
#0 0xef188244 in _libc_kill () from /usr/lib/libc.so.1
#1 0x96f38 in fatal_error_signal (sig=11) at emacs.c:293
#2 <signal handler called>
#3 0xb8b90 in Fmake_charset (name=5650436, doc_string=4916468, props=5138976)
at mule-charset.c:515
#4 0x9bcfc in Ffuncall (nargs=3, args=0xefffcefc) at eval.c:3218
#5 0x6d37c in execute_optimized_program (
program=0xefffcfbf "\210ª\034\bǶ«\027ÈÃ!¬\022ÉÊÃËÌÍÌ\211ÎÏÐÑÅ&\t#\210Ê\207\003",
stack_depth=3, constants_data=0x579490) at bytecode.c:747
#6 0x70650 in Fbyte_code (instructions=-268447824, constants=5739648, stack_depth=27)
at bytecode.c:2404
#7 0x9b624 in Feval (form=5140008) at eval.c:3018
#8 0x1349d8 in readevalloop (readcharfun=4462592, sourcename=3709556, evalfun=0x9b0d0 <Feval>,
printflag=0) at lread.c:1448
#9 0x133964 in Fload_internal (file=3709556, no_error=-286511952, nomessage=-286512600,
nosuffix=-286511952, codesys=-286568592, used_codesys=-286511952) at lread.c:736
#10 0x9bd5c in Ffuncall (nargs=-1, args=0xefffd5bc) at eval.c:3218
#11 0x6d37c in execute_optimized_program (program=0xeefa91fa "+\207\026\035~\200",
stack_depth=5, constants_data=0xeef6ecd0) at bytecode.c:747
#12 0x6cfd4 in funcall_compiled_function (fun=-285645596, nargs=4, args=0xefffd7a4)
at bytecode.c:516
#13 0x9beb0 in Ffuncall (nargs=4, args=0xefffd7a0) at eval.c:3253
#14 0x9ec7c in call4 (fn=-286588680, arg0=3709556, arg1=-286511952, arg2=-286512600,
arg3=-286511952) at eval.c:3919
#15 0xf96e0 in Frequire (feature=4958180, file_name=-286511952) at fns.c:1257
#16 0x9bce4 in Ffuncall (nargs=-1, args=0xefffd95c) at eval.c:3218
#17 0x6d37c in execute_optimized_program (program=0xefffda92 "\207", stack_depth=1,
constants_data=0x4cde10) at bytecode.c:747
#18 0x70650 in Fbyte_code (instructions=-268445192, constants=5037568, stack_depth=15)
at bytecode.c:2404
#19 0x9b624 in Feval (form=3849240) at eval.c:3018
#20 0x1349d8 in readevalloop (readcharfun=4744192, sourcename=4092532, evalfun=0x9b0d0 <Feval>,
printflag=0) at lread.c:1448
#21 0x133964 in Fload_internal (file=4092532, no_error=-286511952, nomessage=-286511952,
nosuffix=-286511952, codesys=-286568592, used_codesys=-286511952) at lread.c:736
#22 0x9bd5c in Ffuncall (nargs=-1, args=0xefffe134) at eval.c:3218
#23 0x6d37c in execute_optimized_program (program=0xeefa91fa "+\207\026\035~\200",
stack_depth=5, constants_data=0xeef6ecd0) at bytecode.c:747
#24 0x6cfd4 in funcall_compiled_function (fun=-285645596, nargs=4, args=0xefffe31c)
at bytecode.c:516
#25 0x9beb0 in Ffuncall (nargs=4, args=0xefffe318) at eval.c:3253
#26 0x9ec7c in call4 (fn=-286588680, arg0=4092532, arg1=-286511952, arg2=-286511952,
arg3=-286511952) at eval.c:3919
#27 0x9afbc in do_autoload (fundef=4094772, funname=-286629744) at eval.c:2832
#28 0x9abc4 in Fcommand_execute (cmd=-286629744, record=-286512600, keys=-286511952)
at eval.c:2641
#29 0x9bcfc in Ffuncall (nargs=-1, args=0xefffe59c) at eval.c:3218
#30 0x6d37c in execute_optimized_program (
program=0x54bf58 "\210\016\r<\016\020¬\023Ñ Ò a«\aÓ pa«\006Ô \210ª\004Õ \210Ö×!\036ØÙÆ\016\rA«\004Úª\002Û\016\fÜ\016\r!#\"\210Ö\016\035!\210ÞÙ!*\207Î\016\tÏ\"\207", stack_depth=2,
constants_data=0xeef6b9b4) at bytecode.c:747
#31 0x6cfd4 in funcall_compiled_function (fun=-285650412, nargs=1, args=0xefffe774)
at bytecode.c:516
#32 0x9beb0 in Ffuncall (nargs=1, args=0xefffe770) at eval.c:3253
#33 0x726cc in Fcall_interactively (function=-286604640, record_flag=-286511952,
keys=-286511952) at callint.c:946
#34 0x9ac4c in Fcommand_execute (cmd=-286604640, record=-286511952, keys=-286511952)
at eval.c:2656
#35 0xd6cfc in execute_command_event (command_builder=0x36f2c0, event=4458732)
at event-stream.c:3836
#36 0xd7304 in Fdispatch_event (event=4459892) at event-stream.c:4155
#37 0x798a8 in Fcommand_loop_1 () at cmdloop.c:575
#38 0x79b1c in command_loop_1 (dummy=-286511952) at cmdloop.c:490
#39 0x9877c in condition_case_1 (handlers=-286512144, bfun=0x79b00 <command_loop_1>,
barg=-286511952, hfun=0x79b7c <cmd_error>, harg=-286511952) at eval.c:1644
#40 0x79c8c in command_loop_2 (dummy=-286511952) at cmdloop.c:252
#41 0x9f3e8 in internal_catch (tag=-286696728, func=0x79c40 <command_loop_2>, arg=-286511952,
threw=0x0) at eval.c:1310
#42 0x793f4 in initial_command_loop (load_me=-286511952) at cmdloop.c:301
#43 0x9542c in sort_args (argc=1923072, argv=0xefffefbc) at emacs.c:1872
Recent messages (most recent first):
Parsing BBDB... (frobnicating...)
Parsing BBDB... (reading...)
Parsing BBDB...
Loading bbdb-com...done
Loading bbdb-com...
Loading bbdb-gnus...done
Loading gnus-xmas...done
Loading gnus-xmas...
Loading bbdb-gnus...
Loading efs-cu...done
--
Steven E. Harris
Primus Knowledge Solutions, Inc.
http://www.primus.com
- 3 participants
- 3 comments
Re: redisplay questions...
23 years, 12 months
William M. Perry
William M. Perry
Andy Piper <andy(a)xemacs.org> writes:
> At 09:34 PM 4/29/00 -0500, William M. Perry wrote:
> >Ok, so I've got scrollbars (almost) working, and am going to try and tackle
> >the redisplay weirdness I've been seeing. Basically that consists of:
> >
> >1) Expose events - I _get_ all the expose events I am supposed to, but the
> > text only appears if I obscure the Gtk XEmacs frame with a normal XEmacs
> > frame. If I obscure then expose it using an xterm, everything (bht the
> > modeline) shows up as just the blank background color.
> >
> >2) C-l causes something similar to happen - it redraws the LINE I am on,
> > but everything else (but the modeline) disappears.
> >
> >Does this ring any bells with the redisplay experts (ben, andy, jonathan)?
>
> Presumably your event code calls gtk_redraw_exposed_area? This part isn't
> actually generalised but is in fact called directly from the native event
> loop.
Yes, it does. Right now I am hooking into one of the signals generated by
the widget instead of doing it directly from my new subclass of GtkFixed,
but...
The interesting thing is that if I don't hook the generic 'event' driver,
redisplay works. But then of course I don't get any input from the
user. :) Ought to be an interesting day. :)
-Bill P.
- 1 participants
- 0 comments
Re: Fix new PCL-CVS
23 years, 12 months
Gunnar Evermann
Gunnar Evermann
sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes:
> 2000-04-30 Mike Sperber <mike(a)xemacs.org>
>
> * cvs-compat.el (cvs-prepare-diff-mode): Fix; t'was broken before.
thanks, this works much better now.
I still have some problems with diff-mode (which I have never used
before), though.
- get a diff from cvs by pressing '='
- in diff window press 'n'
- press 'f' to go to file
Signaling: (wrong-type-argument stringp nil)
expand-file-name(nil)
find-file-noselect(nil)
find-file(nil)
diff-find-file(nil)
call-interactively(diff-find-file)
for reference the diff output is given below.
pressing 'q' in the diff window gives:
Signaling: (error "No buffer named *Diff Output*")
kill-buffer("*Diff Output*")
#<compiled-function nil "...(7)" [kill-buffer "*Diff Output*" diff-cleanup-buffers] 2 ("/tools/emacs/lib/xemacs/xemacs-packages/lisp/dired/diff.elc" . 14678) nil>()
call-interactively(diff-quit)
the name of the buffer is '*cvs-diff*'
hope this helps -- sorry, I have no time to fix it myself.
Gunnar
- 1 participants
- 0 comments
redisplay questions...
23 years, 12 months
William M. Perry
William M. Perry
Ok, so I've got scrollbars (almost) working, and am going to try and tackle
the redisplay weirdness I've been seeing. Basically that consists of:
1) Expose events - I _get_ all the expose events I am supposed to, but the
text only appears if I obscure the Gtk XEmacs frame with a normal XEmacs
frame. If I obscure then expose it using an xterm, everything (bht the
modeline) shows up as just the blank background color.
2) C-l causes something similar to happen - it redraws the LINE I am on,
but everything else (but the modeline) disappears.
Does this ring any bells with the redisplay experts (ben, andy, jonathan)?
Thanks all!
-Bill P.
- 3 participants
- 2 comments
gutter garbage insanity
23 years, 12 months
Ben Wing
Ben Wing
Andy, your gutter implementation needs some serious profiling for garbage
collection.
i was noticing that my xemacs was getting slower and slower as more buffers were
opened --
and then i noticed that if i moved the mouse back and forth, xemacs was garbage
collecting *every fucking second*!
sure enough, with gutters off, the gc goes away, and everything speeds up
immensely.
i have 60 buffers open, and the gutter code is generating 500,000 bytes of
garbage every second!
what the hell?
andy, at the very least use frame-modified-tick to avoid this massive
recalculation.
--
Ben
In order to save my hands, I am cutting back on my mail. I also write
as succinctly as possible -- please don't be offended. If you send me
mail, you _will_ get a response, but please be patient, especially for
XEmacs-related mail. If you need an immediate response and it is not
apparent in your message, please say so. Thanks for your understanding.
See also http://www.666.com/ben/typing.html.
- 4 participants
- 9 comments
Re: Emacs keybinding guide
23 years, 12 months
Adrian Aichner
Adrian Aichner
>>>>> "Jari" == Jari Aalto+mail emacs <jari.aalto(a)poboxes.com> writes:
Jari> 2.2 Emacs versions and keybinding syntax compatibility table:
Hello Jari,
thanks for the summary!
The latest official release of XEmacs is 21.1, currently being at 21.1.9.
I couldn't fill below table off the top of my little head, but maybe
people from xemacs-beta can?
This would surely be worth an update to your guide.
Do you have a test-case for key-binding syntax compatibility?
I could run it and report back.
Best regards,
Adrian
Jari> m-1 : recognizes Emacs styled mouse binding, mouse-1
Jari> b1 : recognizes XEmacs styled mouse binding, button1
Jari> r-k-m : read-kbd-macro
Jari> _yes : works 95% , but there are known bugs.
Jari> ------------------------------------------------------
Jari> style: [] [()] m-1 b1 r-k-m kbd
Jari> ------------------------------------------------------
Jari> Emacs 19.28-30 yes no yes no no no
Jari> Emacs 19.31-33 yes yes yes no bugs no
Jari> Emacs 19.34 yes yes yes no _yes no
Jari> Emacs 20.1-3 yes yes yes ? yes yes
Jari> ------------------------------------------------------
Jari> XEmacs 19.13-14 no yes no yes no no
Jari> XEmacs 19.15-16 no yes _yes yes yes no
Jari> XEmacs 20.2-5 no yes yes yes yes yes
Jari> ------------------------------------------------------
- 1 participants
- 0 comments
Debian GNU/Linux -- vflib3
23 years, 12 months
Karl M. Hegbloom
Karl M. Hegbloom
Might this be useful?
> http://www.debian.org/Packages/unstable/libs/vflib3.html
- 2 participants
- 1 comments
The TeX-Guy Project
24 years
Karl M. Hegbloom
Karl M. Hegbloom
Tell me when to quit...
> http://TypeHack.aial.hiroshima-u.ac.jp/TeX-Guy/
- 1 participants
- 0 comments