comparison man/xemacs-faq.texi @ 563:183866b06e0b

[xemacs-hg @ 2001-05-24 07:50:48 by ben] Makefile.in.in, abbrev.c, alloc.c, buffer.c, bytecode.c, callint.c, callproc.c, casetab.c, chartab.c, cmdloop.c, cmds.c, console-msw.c, console-msw.h, console-stream.c, console-tty.c, console-x.c, console.c, data.c, database.c, debug.c, device-gtk.c, device-msw.c, device-tty.c, device-x.c, device.c, dialog-gtk.c, dialog-msw.c, dialog-x.c, dialog.c, dired-msw.c, dired.c, doc.c, doprnt.c, dragdrop.c, editfns.c, eldap.c, eldap.h, elhash.c, emacs-widget-accessors.c, emacs.c, emodules.c, esd.c, eval.c, event-Xt.c, event-gtk.c, event-msw.c, event-stream.c, events.c, extents.c, faces.c, file-coding.c, fileio.c, filelock.c, floatfns.c, fns.c, font-lock.c, frame-gtk.c, frame-x.c, frame.c, general-slots.h, glade.c, glyphs-gtk.c, glyphs-msw.c, glyphs-widget.c, glyphs-x.c, glyphs.c, glyphs.h, gpmevent.c, gui-gtk.c, gui-x.c, gui.c, gutter.c, hpplay.c, indent.c, input-method-xlib.c, insdel.c, intl.c, keymap.c, libsst.c, libsst.h, linuxplay.c, lisp.h, lread.c, lstream.c, lstream.h, macros.c, marker.c, md5.c, menubar-gtk.c, menubar-msw.c, menubar-x.c, menubar.c, minibuf.c, miscplay.c, miscplay.h, mule-ccl.c, mule-charset.c, mule-wnnfns.c, mule.c, nas.c, ntplay.c, ntproc.c, objects-gtk.c, objects-msw.c, objects-x.c, objects.c, postgresql.c, print.c, process-nt.c, process-unix.c, process.c, ralloc.c, rangetab.c, redisplay.c, scrollbar.c, search.c, select-gtk.c, select-x.c, select.c, sgiplay.c, sheap.c, sound.c, specifier.c, sunplay.c, symbols.c, symeval.h, symsinit.h, syntax.c, sysdep.c, toolbar-msw.c, toolbar.c, tooltalk.c, ui-byhand.c, ui-gtk.c, undo.c, unexaix.c, unexapollo.c, unexconvex.c, unexec.c, widget.c, win32.c, window.c: -- defsymbol -> DEFSYMBOL. -- add an error type to all errors. -- eliminate the error functions in eval.c that let you just use Qerror as the type. -- redo the error API to be more consistent, sensibly named, and easier to use. -- redo the error hierarchy somewhat. create new errors: structure-formation-error, gui-error, invalid-constant, stack-overflow, out-of-memory, process-error, network-error, sound-error, printing-unreadable-object, base64-conversion- error; coding-system-error renamed to text-conversion error; some others. -- fix Mule problems in error strings in emodules.c, tooltalk.c. -- fix error handling in mswin open-network-stream. -- Mule-ize all sound files and clean up the headers. -- nativesound.h -> sound.h and used for all sound files. -- move some shared stuff into glyphs-shared.c: first attempt at eliminating some of the massive GTK code duplication. xemacs.mak: add glyphs-shared.c. xemacs-faq.texi: document how to debug X errors subr.el: fix doc string to reflect reality
author ben
date Thu, 24 May 2001 07:51:33 +0000
parents 52626a2f02ef
children 5fd7ba8b56e7
comparison
equal deleted inserted replaced
562:c775bd016b32 563:183866b06e0b
5 @setchapternewpage off 5 @setchapternewpage off
6 @c %**end of header 6 @c %**end of header
7 @finalout 7 @finalout
8 @titlepage 8 @titlepage
9 @title XEmacs FAQ 9 @title XEmacs FAQ
10 @subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2001/04/20 11:32:18 $ 10 @subtitle Frequently asked questions about XEmacs @* Last Modified: $Date: 2001/05/24 07:50:53 $
11 @sp 1 11 @sp 1
12 @author Tony Rossini <rossini@@biostat.washington.edu> 12 @author Tony Rossini <rossini@@biostat.washington.edu>
13 @author Ben Wing <ben@@xemacs.org> 13 @author Ben Wing <ben@@xemacs.org>
14 @author Chuck Thompson <cthomp@@xemacs.org> 14 @author Chuck Thompson <cthomp@@xemacs.org>
15 @author Steve Baur <steve@@xemacs.org> 15 @author Steve Baur <steve@@xemacs.org>
167 * Q2.1.13:: HP/UX 10.10 and @code{create_process} failure 167 * Q2.1.13:: HP/UX 10.10 and @code{create_process} failure
168 * Q2.1.14:: @kbd{C-g} doesn't work for me. Is it broken? 168 * Q2.1.14:: @kbd{C-g} doesn't work for me. Is it broken?
169 * Q2.1.15:: How to debug an XEmacs problem with a debugger. 169 * Q2.1.15:: How to debug an XEmacs problem with a debugger.
170 * Q2.1.16:: XEmacs crashes in @code{strcat} on HP/UX 10. 170 * Q2.1.16:: XEmacs crashes in @code{strcat} on HP/UX 10.
171 * Q2.1.17:: @samp{Marker does not point anywhere}. 171 * Q2.1.17:: @samp{Marker does not point anywhere}.
172 * Q2.1.18:: [This question intentionally left blank] 172 * Q2.1.18:: XEmacs is outputting lots of X errors.
173 * Q2.1.19:: XEmacs does not follow the local timezone. 173 * Q2.1.19:: XEmacs does not follow the local timezone.
174 * Q2.1.20:: @samp{Symbol's function definition is void: hkey-help-show.} 174 * Q2.1.20:: @samp{Symbol's function definition is void: hkey-help-show.}
175 * Q2.1.21:: [This question intentionally left blank] 175 * Q2.1.21:: [This question intentionally left blank]
176 * Q2.1.22:: XEmacs seems to take a really long time to do some things. 176 * Q2.1.22:: XEmacs seems to take a really long time to do some things.
177 * Q2.1.23:: Movemail on Linux does not work for XEmacs 19.15 and later. 177 * Q2.1.23:: Movemail on Linux does not work for XEmacs 19.15 and later.
1222 * Q2.1.13:: HP/UX 10.10 and @code{create_process} failure 1222 * Q2.1.13:: HP/UX 10.10 and @code{create_process} failure
1223 * Q2.1.14:: @kbd{C-g} doesn't work for me. Is it broken? 1223 * Q2.1.14:: @kbd{C-g} doesn't work for me. Is it broken?
1224 * Q2.1.15:: How to debug an XEmacs problem with a debugger. 1224 * Q2.1.15:: How to debug an XEmacs problem with a debugger.
1225 * Q2.1.16:: XEmacs crashes in @code{strcat} on HP/UX 10. 1225 * Q2.1.16:: XEmacs crashes in @code{strcat} on HP/UX 10.
1226 * Q2.1.17:: @samp{Marker does not point anywhere}. 1226 * Q2.1.17:: @samp{Marker does not point anywhere}.
1227 * Q2.1.18:: [This question intentionally left blank] 1227 * Q2.1.18:: XEmacs is outputting lots of X errors.
1228 * Q2.1.19:: XEmacs does not follow the local timezone. 1228 * Q2.1.19:: XEmacs does not follow the local timezone.
1229 * Q2.1.20:: @samp{Symbol's function definition is void: hkey-help-show.} 1229 * Q2.1.20:: @samp{Symbol's function definition is void: hkey-help-show.}
1230 * Q2.1.21:: [This question intentionally left blank] 1230 * Q2.1.21:: [This question intentionally left blank]
1231 * Q2.1.22:: XEmacs seems to take a really long time to do some things. 1231 * Q2.1.22:: XEmacs seems to take a really long time to do some things.
1232 * Q2.1.23:: Movemail on Linux does not work for XEmacs 19.15 and later. 1232 * Q2.1.23:: Movemail on Linux does not work for XEmacs 19.15 and later.
2012 Here are some hints: 2012 Here are some hints:
2013 2013
2014 @itemize @bullet 2014 @itemize @bullet
2015 @item 2015 @item
2016 First of all, if the crash is at all reproducible, consider very 2016 First of all, if the crash is at all reproducible, consider very
2017 strongly recompiling your XEmacs with debugging symbols, with no 2017 strongly recompiling your XEmacs with debugging symbols and with no
2018 optimization, and with the configure options @samp{--debug=yes} and 2018 optimization (e.g. with GCC use the compiler flags @samp{-g -O0} --
2019 @samp{--error-checking=all}. This will make your XEmacs run somewhat 2019 that's an "oh" followed by a zero), and with the configure options
2020 slower but make it a lot more likely to catch the problem earlier 2020 @samp{--debug=yes} and @samp{--error-checking=all}. This will make your
2021 (closer to its source), and a lot easier to determine what's going on 2021 XEmacs run somewhat slower but make it a lot more likely to catch the
2022 with a debugger. 2022 problem earlier (closer to its source), and a lot easier to determine
2023 what's going on with a debugger.
2023 2024
2024 @item 2025 @item
2025 If you're able to run XEmacs under a debugger and reproduce the crash 2026 If you're able to run XEmacs under a debugger and reproduce the crash
2026 (if it's inconvenient to do this because XEmacs is already running or is 2027 (if it's inconvenient to do this because XEmacs is already running or is
2027 running in batch mode as part of a bunch of scripts, consider attaching 2028 running in batch mode as part of a bunch of scripts, consider attaching
2036 2037
2037 @item 2038 @item
2038 If XEmacs is hitting some weird Lisp error that's causing it to crash 2039 If XEmacs is hitting some weird Lisp error that's causing it to crash
2039 (e.g. during startup), put a breakpoint on @code{signal_1()}---this is 2040 (e.g. during startup), put a breakpoint on @code{signal_1()}---this is
2040 declared static in eval.c. 2041 declared static in eval.c.
2042
2043 @item
2044 If XEmacs is outputting lots of X errors, put a breakpoint on
2045 @code{x_error_handler()}; that will tell you which call is causing them.
2041 2046
2042 @item 2047 @item
2043 Internally, you will probably see lots of variables that hold objects of 2048 Internally, you will probably see lots of variables that hold objects of
2044 type @code{Lisp_Object}. These are exactly what they appear to be, 2049 type @code{Lisp_Object}. These are exactly what they appear to be,
2045 i.e. references to Lisp objects. Printing them out with the debugger 2050 i.e. references to Lisp objects. Printing them out with the debugger
2217 A problem with some early versions of Gnus 5.4 caused this error. 2222 A problem with some early versions of Gnus 5.4 caused this error.
2218 Upgrade your Gnus. 2223 Upgrade your Gnus.
2219 @end enumerate 2224 @end enumerate
2220 2225
2221 @node Q2.1.18, Q2.1.19, Q2.1.17, Installation 2226 @node Q2.1.18, Q2.1.19, Q2.1.17, Installation
2222 @unnumberedsubsec Q2.1.18: removed 2227 @unnumberedsubsec Q2.1.18: XEmacs is outputting lots of X errors.
2228
2229 If this is happening, we would very much like to know what's causing
2230 them. To find this out, @xref{Q2.1.15}. Try to get both a C and Lisp
2231 backtrace, and send them to @email{xemacs-beta@@xemacs.org}.
2223 2232
2224 @node Q2.1.19, Q2.1.20, Q2.1.18, Installation 2233 @node Q2.1.19, Q2.1.20, Q2.1.18, Installation
2225 @unnumberedsubsec Q2.1.19: XEmacs does not follow the local timezone. 2234 @unnumberedsubsec Q2.1.19: XEmacs does not follow the local timezone.
2226 2235
2227 When using one of the prebuilt binaries many users have observed that 2236 When using one of the prebuilt binaries many users have observed that