Re: Debugging 64bit xemacs (beta, latest cvs) on sparc64 (Sun T1000)
17 years, 12 months
Aidan Kehoe
Aidan Kehoe
Ar an chéad lá de mí na Nollaig, scríobh Andrew Walrond:
> > Nothing comes to mind as a likely source of the problem; memcpy
> > shouldn’t have alignment restrictions. The crash takes place during a
> > call of the Lisp function command-error: if you do an xemacs -vanilla ,
> > then evaluate
> >
> > (command-error (cons 'quit "Hi there"))
> >
> > in *scratch*, do you see it?
> >
>
> Hmm, I get
> Peculiar error (quit . "Hi there")t
That’s as it should be. One more bug that isn’t as co-operative as we would
like:-)
> Looks like a quote mismatch (unbalanced '). I tried a few combinations
> without any luck (I don't know lisp so its not obvious to me).
'some-string means ‘treate “some-string” as a symbol name.’ From the
internals manual:
A symbol is basically just an object with four fields: a name (a
string), a value (some Lisp object), a function (some Lisp object), and
a property list (usually a list of alternating keyword/value pairs).
What makes symbols special is that there is usually only one symbol with
a given name, and the symbol is referred to by name. This makes a
symbol a convenient way of calling up data by name, i.e. of implementing
variables. (The variable’s value is stored in the “value slot”.)
Similarly, functions are referenced by name, and the definition of the
function is stored in a symbol’s “function slot”. This means that
there can be a distinct function and variable with the same name. The
property list is used as a more general mechanism of associating
additional values with particular names, and once again the namespace is
independent of the function and variable namespaces.
See http://www.xemacs.org/Documentation/beta/html/internals_22.html if
you’re curious.
--
Santa Maradona, priez pour moi!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Heavy load under native win32 xemacs 21.5
17 years, 12 months
Fabrice Popineau
Fabrice Popineau
Hi,
For quite a long time, I have observed that xemacs may turn up to
consume CPU even doing nothing (in the range 25%-95%). I have not tried
to reproduce that under vanilla xemacs, my usual configuration runs gnus
and buffers to edit program files.
I have used spy++ to look at the messages sent to the xemacs window, and
there is a real high number of WM_CTLCOLORSCROLLBAR messages processed,
which seems a bit strange to me. Is there any reason for that ? I don't
see why messages should be processed while doing nothing.
Any insight on this problem would be welcome,
Greetings,
--
Fabrice
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
- 3 participants
- 3 comments