Re: Status of bugs in bug tracking system?
23 years, 9 months
Reid Rivenburgh
Reid Rivenburgh
Stephen J Turnbull writes:
Reid> I'm currently using version 21.1.14 and still seeing the
Reid> problem.
I forgot to also note that it happened with 21.2.3x when I tried that
some time ago, too. Now I don't feel bad about posting to the beta
list!
> Good! I mean, that's too bad, but if you could find a simple
> recipe to repeat the problem, post it here, we'll have a much
> better chance at isolating it. If you have nothing else, please
> repost the report here.
I'm unable to consistently trigger the bug, which is why I figured
it's pretty obscure. I've also never seen it other than when I send
mail with Gnus. Sorry I can't provide a recipe. I will append my bug
report, if anyone is interested. It contains the details and a gdb
backtrace.
> My deepest apologies; I'll take a look at systematizing this stuff
> in a few days, and I'll look at your bug at some point regardless
> of what you do, but I've _got_ to get release stuff out now, and
> then do some day job.
I understand. I've waited this long to ask because I didn't want to
seem too forward. I know everyone has day jobs and other priorities,
unfortunately....
Thanks for your reply.
Reid
- 1 participants
- 0 comments
More XEmacs/GTK patches commited to the branch...
23 years, 9 months
William M. Perry
William M. Perry
The GTK redisplay backend now builds & runs. No funky widgets yet, but
that should be fairly simple.
This builds on my 3 boxes here (freebsd 4.2, solaris 2.7, linux 2.4 (debian
unstable)) in all its glory.
Could other people please test it on their machines? Thanks.
-Bill P.
- 5 participants
- 8 comments
question about the widget instantiation...
23 years, 9 months
William M. Perry
William M. Perry
I've got the widget infrastructure code written, and just need to write all
the instantiators. Which thanks to the GTK lisp bindings, I could do all
in lisp, similar to how I did all the dialog work in 21.1.
So... is it illegal to call lisp code from within an image instantiator?
Ben? Andy? I know you cannot call it from within redisplay, but I'm not
clear on whether the instantiators are called during redisplay or
beforehand.
Thanks!
-Bill P.
- 2 participants
- 2 comments
Re: loadup.el, You LIE! (21.2.42 + a few hours CVS]
23 years, 9 months
Michael Sperber
Michael Sperber
>>>>> "Moiself" == Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes:
>>>>> "SY" == Steve Youngs <youngs(a)xemacs.org> writes:
SY> |--==> "MS" == Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes:
MS> You're right, but the code in question was written at a time where we
MS> *had* to get at the packages because of the dumped-lisp files. Once
MS> they go away completely, I'm all for scratching all the code
MS> associated with it.
MS> Steve (Youngs, that is): are there any left?
SY> I'm pretty sure that there aren't. The XEmacs I built after my hard
SY> drive crash was built without *any* packages installed. It built and
SY> ran fine.
Moiself> That wasn't the question: the question is if building *with* packages
Moiself> installed still finds any dumped-lisp.el files there. If it doesn't,
Moiself> Steve and I would rather remove the code silliness associated with it
Moiself> entirely, a plan Steve Baur and I hatched a long time ago.
So, the only one left seems to be egg-its. Could the MULE folks
and/or Stephen comment on how this is handled?
- Do we need to dump with the stuff in dumped-lisp?
- Could we do it with auto-autoloads instead?
- Do XEmacs/MULE binary packages ship with egg-its dumped?
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
- 1 participants
- 0 comments
21.1.14 vs. alphaev5-dec-osf5.0
23 years, 9 months
John H Palmieri
John H Palmieri
I've been running various versions of XEmacs 21.2 lately, but I
thought I would try getting the new release 21.1.14, just for kicks.
When I tried to configure it, I got this message:
./configure: XEmacs hasn't been ported to `alphaev5-dec-osf5.0' systems.
./configure: Check `etc/MACHINES' for recognized configuration names.
'./configure ... alpha-dec-osf1' worked, sort of (the tests in 'make
check' report 100% success, but then it hangs; otherwise, xemacs seems
to run okay). Is it worthwhile fixing configure to recognize
alphaev5-dec-osf5.0?
(On a related topic, should /etc/MACHINES be updated in version
21.2.43, to reflect the fact that alphaev5-dec-osf5.0 is recognized by
configure?)
--
John H. Palmieri
Dept of Mathematics, Box 354350 palmieri(a)math.washington.edu
University of Washington http://www.math.washington.edu/~palmieri/
Seattle, WA 98195-4350
- 3 participants
- 4 comments
Can't build xemacs-21.1.14
23 years, 9 months
Norbert Koch
Norbert Koch
Hi!
On FreeBSD 4.2-RELEASE (no problems on FreeBSD 3.3-RELEASE), after
applying the 21.1.13-21.1.14.patch and reconfiguring with
./configure --prefix=/sw/i386_fbsd3/xemacs-21.1 \
'--site-includes=/client/include /usr/local/include' \
'--site-libraries=/client/lib /usr/local/lib' \
--use-union-type \
--with-mule
temacs dumps core. Anything you want me to investigate in?
norbert.
EMACSBOOTSTRAPLOADPATH="/sw/src/nk/xemacs-21.1.13/src/../lisp/:/sw/src/nk/xemacs-21.1.13" ./temacs -batch -l /sw/src/nk/xemacs-21.1.13/src/../lisp/update-elc.el
Loading /sw/src/nk/xemacs-21.1.13/src/../lisp/update-elc.el...
Loading very-early-lisp... (1860)
Loading find-paths.el... (10464)
Loading packages.el... (18812)
Loading setup-paths.el... (4120)
Loading dump-paths.el... (0)
Loading
/usr/local/sw/src/nk/xemacs-21.1.13/src/../lisp/dumped-lisp.el...Floating
point exception - core dumped
gmake[1]: *** [update-elc.stamp] Error 136
gmake[1]: Leaving directory `/usr/local/sw/src/nk/xemacs-21.1.13/src'
gmake: *** [src] Error 2
#0 0x80775f7 in Dynarr_resize (d=0x83ebc40, size=82) at dynarr.c:136
#1 0x80a79bc in decode_coding_no_conversion (decoding=0x83ff600,
src=0x842e052 "defsubst etc.\n\t\"bytecomp-runtime\"\t; define
defsubst\n\t\"Installation.el\"\n\t\"find-paths\"\n\t\"packages\"\t\t; Bootstrap run-time lisp environment\n\t\"setup-paths\"\n\t\"dump-paths\"\n\t\"subr\" \t\t\t; load the most basic Li"..., dst=0x83ebc40, n=6974) at file-coding.c:4446
#2 0x80a345d in mule_decode (decoding=0x83ff600,
src=0x842e000 "(setq preloaded-file-list\n (assemble-list\n
\"backquote\" \t\t; needed for defsubst
etc.\n\t\"bytecomp-runtime\"\t; define
defsubst\n\t\"Installation.el\"\n\t\"find-paths\"\n\t\"packages\"\t\t; Bootstrap run-time"..., dst=0x83ebc40, n=7056) at file-coding.c:2031
#3 0x80a9ee4 in decoding_reader (stream=0x83ff600,
data=0x842e000 "(setq preloaded-file-list\n (assemble-list\n
\"backquote\" \t\t; needed for defsubst
etc.\n\t\"bytecomp-runtime\"\t; define
defsubst\n\t\"Installation.el\"\n\t\"find-paths\"\n\t\"packages\"\t\t; Bootstrap run-time"..., size=8192) at file-coding.c:1814
#4 0x8100adf in Lstream_raw_read (lstr=0x83ff600,
buffer=0x842e000 "(setq preloaded-file-list\n
(assemble-list\n \"backquote\" \t\t; needed for defsubst
etc.\n\t\"bytecomp-runtime\"\t; define
defsubst\n\t\"Installation.el\"\n\t\"find-paths\"\n\t\"packages\"\t\t; Bootstrap run-time"..., size=8192) at lstream.c:509
#5 0x8100be5 in Lstream_read (lstr=0x83ff600, data=0xbfbfee03,
#size=1)
at lstream.c:527
#6 0x810158b in Lstream_fgetc (lstr=0x83ff600) at lstream.c:742
#7 0x80fb751 in readchar (readcharfun={gu = {val = 138409472, markbit
#= 0,
type = Lisp_Type_Record}, s = {val = -130025984, bits = 2}, u
= {
val = 138409472, bits = 2}, ui = 675280384, i = 675280384,
v = 0x283ff600, cv = 0x283ff600}) at lread.c:256
#8 0x80fd159 in readevalloop (readcharfun={gu = {val = 138409472,
markbit = 0, type = Lisp_Type_Record}, s = {val = -130025984,
bits = 2}, u = {val = 138409472, bits = 2}, ui = 675280384,
i = 675280384, v = 0x283ff600, cv = 0x283ff600}, sourcename={gu
= {
val = 138420780, markbit = 0, type = Lisp_Type_String}, s = {
val = -130014676, bits = 6}, u = {val = 138420780, bits = 6},
ui = 1749033516, i = 1749033516, v = 0x6840222c, cv =
0x6840222c},
evalfun=0x8082a54 <Feval>, printflag=0) at lread.c:1307
#9 0x80fc43f in Fload_internal (file={gu = {val = 138420780, markbit
#= 0,
type = Lisp_Type_String}, s = {val = -130014676, bits = 6}, u
= {
val = 138420780, bits = 6}, ui = 1749033516, i = 1749033516,
v = 0x6840222c, cv = 0x6840222c}, no_error={gu = {val =
138084356,
markbit = 0, type = Lisp_Type_Symbol}, s = {val = -130351100,
bits = 10}, u = {val = 138084356, bits = 10}, ui = 2822438916,
i = -1472528380, v = 0xa83b0004, cv = 0xa83b0004}, nomessage={gu
= {
val = 138084356, markbit = 0, type = Lisp_Type_Symbol}, s = {
val = -130351100, bits = 10}, u = {val = 138084356, bits =
10},
ui = 2822438916, i = -1472528380, v = 0xa83b0004, cv =
0xa83b0004},
nosuffix={gu = {val = 138084356, markbit = 0, type =
Lisp_Type_Symbol},
s = {val = -130351100, bits = 10}, u = {val = 138084356, bits =
10},
ui = 2822438916, i = -1472528380, v = 0xa83b0004, cv =
0xa83b0004},
codesys={gu = {val = 138084356, markbit = 0, type =
Lisp_Type_Symbol},
s = {val = -130351100, bits = 10}, u = {val = 138084356, bits =
10},
ui = 2822438916, i = -1472528380, v = 0xa83b0004, cv =
0xa83b0004},
used_codesys={gu = {val = 138084356, markbit = 0,
type = Lisp_Type_Symbol}, s = {val = -130351100, bits = 10}, u
= {
val = 138084356, bits = 10}, ui = 2822438916, i = -1472528380,
v = 0xa83b0004, cv = 0xa83b0004}) at lread.c:747
#10 0x8083313 in Feval (form={gu = {val = 138560324, markbit = 0,
type = Lisp_Type_Cons}, s = {val = -129875132, bits = 4}, u =
{
val = 138560324, bits = 4}, ui = 1212302148, i = 1212302148,
v = 0x48424344, cv = 0x48424344}) at eval.c:3063
#11 0x8081022 in Flet (args={gu = {val = 138560316, markbit = 0,
type = Lisp_Type_Cons}, s = {val = -129875140, bits = 4}, u =
{
val = 138560316, bits = 4}, ui = 1212302140, i = 1212302140,
v = 0x4842433c, cv = 0x4842433c}) at eval.c:758
#12 0x8082fa7 in Feval (form={gu = {val = 138560292, markbit = 0,
type = Lisp_Type_Cons}, s = {val = -129875164, bits = 4}, u =
{
val = 138560292, bits = 4}, ui = 1212302116, i = 1212302116,
v = 0x48424324, cv = 0x48424324}) at eval.c:2997
#13 0x80fd234 in readevalloop (readcharfun={gu = {val = 138340352,
markbit = 0, type = Lisp_Type_Record}, s = {val = -130095104,
bits = 2}, u = {val = 138340352, bits = 2}, ui = 675211264,
i = 675211264, v = 0x283ee800, cv = 0x283ee800}, sourcename={gu
= {
val = 138320668, markbit = 0, type = Lisp_Type_String}, s = {
val = -130114788, bits = 6}, u = {val = 138320668, bits = 6},
ui = 1748933404, i = 1748933404, v = 0x683e9b1c, cv =
0x683e9b1c},
evalfun=0x8082a54 <Feval>, printflag=0) at lread.c:1341
#14 0x80fc43f in Fload_internal (file={gu = {val = 138320668, markbit
#= 0,
type = Lisp_Type_String}, s = {val = -130114788, bits = 6}, u
= {
val = 138320668, bits = 6}, ui = 1748933404, i = 1748933404,
v = 0x683e9b1c, cv = 0x683e9b1c}, no_error={gu = {val =
138084356,
markbit = 0, type = Lisp_Type_Symbol}, s = {val = -130351100,
bits = 10}, u = {val = 138084356, bits = 10}, ui = 2822438916,
i = -1472528380, v = 0xa83b0004, cv = 0xa83b0004}, nomessage={gu
= {
val = 138084356, markbit = 0, type = Lisp_Type_Symbol}, s = {
val = -130351100, bits = 10}, u = {val = 138084356, bits =
10},
ui = 2822438916, i = -1472528380, v = 0xa83b0004, cv =
0xa83b0004},
nosuffix={gu = {val = 138084356, markbit = 0, type =
Lisp_Type_Symbol},
s = {val = -130351100, bits = 10}, u = {val = 138084356, bits =
10},
ui = 2822438916, i = -1472528380, v = 0xa83b0004, cv =
0xa83b0004},
codesys={gu = {val = 138084356, markbit = 0, type =
Lisp_Type_Symbol},
s = {val = -130351100, bits = 10}, u = {val = 138084356, bits =
10},
ui = 2822438916, i = -1472528380, v = 0xa83b0004, cv =
0xa83b0004},
used_codesys={gu = {val = 138084356, markbit = 0,
type = Lisp_Type_Symbol}, s = {val = -130351100, bits = 10}, u
= {
val = 138084356, bits = 10}, ui = 2822438916, i = -1472528380,
v = 0xa83b0004, cv = 0xa83b0004}) at lread.c:747
#15 0x8083313 in Feval (form={gu = {val = 138260340, markbit = 0,
type = Lisp_Type_Cons}, s = {val = -130175116, bits = 4}, u =
{
val = 138260340, bits = 4}, ui = 1212002164, i = 1212002164,
v = 0x483daf74, cv = 0x483daf74}) at eval.c:3063
#16 0x8087805 in condition_case_1 (handlers={gu = {val = 138084452,
markbit = 0, type = Lisp_Type_Symbol}, s = {val = -130351004,
bits = 10}, u = {val = 138084452, bits = 10}, ui = 2822439012,
i = -1472528284, v = 0xa83b0064, cv = 0xa83b0064},
bfun=0x8082a54 <Feval>, barg={gu = {val = 138260340, markbit = 0,
type = Lisp_Type_Cons}, s = {val = -130175116, bits = 4}, u =
{
val = 138260340, bits = 4}, ui = 1212002164, i = 1212002164,
v = 0x483daf74, cv = 0x483daf74}, hfun=0x8067fbc <cmd_error>,
harg={
gu = {val = 138084356, markbit = 0, type = Lisp_Type_Symbol}, s
= {
val = -130351100, bits = 10}, u = {val = 138084356, bits =
10},
ui = 2822438916, i = -1472528380, v = 0xa83b0004, cv =
0xa83b0004})
at eval.c:1653
#17 0x8068043 in top_level_1 (dummy={gu = {val = 138084356, markbit =
#0,
type = Lisp_Type_Symbol}, s = {val = -130351100, bits = 10}, u
= {
val = 138084356, bits = 10}, ui = 2822438916, i = -1472528380,
v = 0xa83b0004, cv = 0xa83b0004}) at cmdloop.c:206
#18 0x8087710 in internal_catch (tag={gu = {val = 138166372, markbit =
#0,
type = Lisp_Type_Symbol}, s = {val = -130269084, bits = 10}, u
= {
val = 138166372, bits = 10}, ui = 2822520932, i = -1472446364,
v = 0xa83c4064, cv = 0xa83c4064}, func=0x8068014 <top_level_1>,
arg={
gu = {val = 138084356, markbit = 0, type = Lisp_Type_Symbol}, s
= {
val = -130351100, bits = 10}, u = {val = 138084356, bits =
10},
ui = 2822438916, i = -1472528380, v = 0xa83b0004, cv =
0xa83b0004},
threw=0x0) at eval.c:1328
#19 0x80678aa in initial_command_loop (load_me={gu = {val = 138320668,
#
markbit = 0, type = Lisp_Type_String}, s = {val = -130114788,
bits = 6}, u = {val = 138320668, bits = 6}, ui = 1748933404,
i = 1748933404, v = 0x683e9b1c, cv = 0x683e9b1c}) at
cmdloop.c:285
#20 0x807eb00 in sort_args (argc=4, argv=0xbfbff8d0) at emacs.c:1725
#21 0x8080312 in main (argc=4, argv=0xbfbff8d0, envp=0xbfbff8e4)
at emacs.c:2080
#22 0x804ec79 in _start ()
- 2 participants
- 3 comments
Re: loadup.el, You LIE! (21.2.42 + a few hours CVS]
23 years, 9 months
Michael Sperber
Michael Sperber
>>>>> "SY" == Steve Youngs <youngs(a)xemacs.org> writes:
SY> |--==> "MS" == Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes:
MS> You're right, but the code in question was written at a time where we
MS> *had* to get at the packages because of the dumped-lisp files. Once
MS> they go away completely, I'm all for scratching all the code
MS> associated with it.
MS> Steve (Youngs, that is): are there any left?
SY> I'm pretty sure that there aren't. The XEmacs I built after my hard
SY> drive crash was built without *any* packages installed. It built and
SY> ran fine.
That wasn't the question: the question is if building *with* packages
installed still finds any dumped-lisp.el files there. If it doesn't,
Steve and I would rather remove the code silliness associated with it
entirely, a plan Steve Baur and I hatched a long time ago.
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
- 1 participants
- 0 comments
21.4 (ex 22.0) Release Status / Call for Testers and Volunteers
23 years, 9 months
Stephen J. Turnbull
Stephen J. Turnbull
** STATUS REPORT
The version number of the March 1 release is being demoted from 22.0
to 21.4, due to late delivery of the merge of GTK+ support to the 21.2
code base, and of the Mule on Windows work being done by Ben Wing.
Inclusion of these features wasn't terribly plausible on the tight
schedule we chose, but it was worth a try. Perhaps related to that
impetus, these features are being actively worked on, and are
scheduled for delivery in the release of 22.0 in the third quarter of
2001. This schedule is realistic on current pace.
In the 21.4 tarballs, GTK support is planned for inclusion on an
untested, unsupported experimental basis. Configuration of the
support will default to _off_, in testing as well as in the release.
Mule on Windows is more problematic. A CVS branch will be created in
the near future, and we hope for a merge into the _21.5 development
branch_ by early spring.
The 21.4 release will include the gutters and widgets feature,
allowing embedding of toolkit widgets in frames and buffers. The
basic framework is fairly solid, but 21.4 will include only minimal,
demonstration-level application code.
The other major feature planned for 21.4 is "SUMO in source kit."
This is intended to address the "OK, I've built it, it starts, but it
doesn't _do_ anything" FAQ. Although the package architecture is
sound, it is still difficult to bootstrap. The default tarball will
include the SUMO package tarball, so that the build will install a
full-featured XEmacs environment. Disaggregated source kits will
still be available for those who prefer to choose what they install,
rather than installing everything then removing what's not wanted.
On the Windows platform, this issue seems to have been successfully
addressed via Andy Piper's port of the Cygwin netinstaller.
Other features' development is generally proceeding on schedule, and
assorted bugs and "pessimizations" have been discovered. Many have
been fixed, others are being worked on.
More details, and information on individual features, will be made
available on the Release Status Page:
http://www.xemacs.org/Releases/Public-21.2/
Discussion of release plans, as well as all other issues related to
XEmacs development, is taking place on the developers' mailing list,
xemacs-beta(a)xemacs.org
xemacs-beta is an open mailing list. You can subscribe from the
XEmacs home page, http://www.xemacs.org/, or by sending a request
containing the word `subscribe' (without quotes) in the _body_ of the
message to xemacs-beta-request(a)xemacs.org. List archives are
available at http://list-archives.xemacs.org/xemacs-beta/.
** RELEASE MANAGER
Yes, I've been out of it for a couple of weeks. "Senior panic" is
over (Japanese students graduate in mid-March), so I'll have more time
to devote to things like monitoring comp.emacs.xemacs, and updating
the release pages.
Specifically management-related tasks like this announcement are
lagging schedule by about a week. However, coding and testing are
proceeding on schedule as far as can be known.
** CALL FOR TESTERS
We need beta testers! Only you can tell us if XEmacs builds and works
well on your system, in the configuration you need. We especially
need to test --with-gtk=no builds on systems that don't support GTK+.
The number one testing priority now is building the gtk-xemacs merged
code, _without_ GTK+ support. To include GTK+ support, even on an
experimental basis, in the release tarballs, we must be sure it has no
adverse impact on the supported code. For details on getting,
building, and testing the GTK+ branch and development mainline, see
http://www.xemacs.org/Releases/Public-21.2/tester.html
Testers should subscribe to xemacs-beta, or review the archives
regularly.
** 22.0 RELEASE
A proposal to release the next version of XEmacs, 22.0, planned to
include support for GTK+ and better integration of Mule with the
Windows I18N API, is in the works. The target will be the end of 3rd
Quarter, 2001.
If you have "big things" in mind for XEmacs, why don't you write up a
"feature proposal" and send it my way? It needn't be something you
personally plan to do. Some people implement their wishes (e.g.,
http://www.xemacs.org/ArchitectingXEmacs/, Ben Wing's "Architecting
XEmacs"); others just publish them (for example, Jamie Zawinski's
"XEmacs Wishlist", http://www.jwz.org/doc/xemacs-wishlist.html).
** CALL FOR VOLUNTEERS
We need workers!
* 22.0 Release Manager
The 21.4 Release Manager plans to retire in April. How would _you_
like to be known for releasing the first XEmacs with GTK and Windows
I18N API support? You _know_ you would! Write me, Stephen Turnbull
<stephen(a)xemacs.org>, and we can talk about your qualifications and
the job's responsibilities. Currently active XEmacs developers
preferred, of course, but it's not an absolute requirement. You
mostly just need to be able to say "no". :-) (It does help to have a
track record as a developer. But there are other ways to establish
credibility.)
Appointment subject to approval of the XEmacs Review Board.
* Bug Tracking System
Gunnar Evermann, our BTS maintainer, is doing the best he can. But
after years of neglect of the BTS, he needs help. There are about
1000 entries in the system. If we can get 5 volunteers to just
_classify_ 10 messages, and prioritize maybe one actual bug, per week,
in six months we'll be on top of the problem. You don't need to be
intimately familiar with XEmacs internals, nor even terribly
technical, to do this. The data doesn't get thrown away, so a few
misclassifications won't hurt anywhere near as much as a little bit of
classification will help.
* Documentation
Much effort has been made to improve the documentation, especially by
Adrian Aichner in creation of the Sourceforge project to handle our
web page, and putting together the bits and pieces that are the XEmacs
FAQ list. Our own "sorceror's apprentice", Martin Buchholz, has been
busily sweeping away typographical lint from comments and docstrings
as he cleans up the code.
But there are many places where XEmacs documentation is inaccurate,
incomplete, inaccessible, or simply nonexistent. All of these are
bugs, and we ask you all to report them, and where possible provide
fixes, just as enthusiastically as you report crashes and
functionality bugs.
* General
We always need people to fix bugs and add features. It's not
necessarily technically hard, especially at the Lisp level. And
XEmacs's development process imposes relatively few political
obstacles.
With the addition of GTK+ support in the near future, we will get
libglade support, allowing use of the Glade UI design tool to
prototype Custom interfaces and dialog boxes. If you have GTK+/GNOME
support on your system, you can install Glade and start prototyping
the XEmacs of the future.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."
- 1 participants
- 0 comments
Lazy lock causes minibuffer issues
23 years, 9 months
Matt Tucker
Matt Tucker
1. xemacs -vanilla
2. (make-frame)
3. (custom-set-variables '(lazy-lock-mode t nil (lazy-lock)))
4. (find-file "~") ;; any file will do
5. Start switching between frame 1 and frame 2, and notice that
the cursor shows up in the minibuffer rather than the appropiate
window (ie, buffer)
Lazy lock also seems to occasionally have serious speed issues when
multiple frames are open.
- 1 participants
- 0 comments
xemacs still core dumps
23 years, 9 months
Albert Ting
Albert Ting
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 (beta43) "Terspichore" [Lucid] (sparc-sun-solaris2.6, Mule) of Mon Feb 5 2001 on betty
configured using `configure --with-mule --with-clash-detection'
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
I had posted this bug in xemacs 21.2.38 and it still core dumps.
Looks like a GC related bug. Running bee-mode (a bigloo/scheme
programming mode), I get a core dump. Can't tell if it's bee-mode
itself, or possibly a font-lock problem.
It's repeatable. Create a dummy file, such as foo.scm:
----------------------------
;; -*- mode: bee; -*-
;;
----------------------------
install bee mode, then run xemacs.
$ xemacs -q
M-x load-library bee-mode
M-x find-file foo.scm
M-x rmail (or vm)
I can post a copy of bee-mode if you like (about 158kb, gzipped).
$ gdb xemacs
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.6"...
(gdb) run -vanilla
Starting program: xemacs-21.2.43/src/xemacs -vanilla
warning: Lowest section in /usr/lib/libintl.so.1 is .dynamic at 0x74
Program received signal SIGSEGV, Segmentation fault.
compact_string_chars () at alloc.c:2960
2960 assert (!(LRECORD_FREE_P (string)));
(gdb) where
#0 compact_string_chars () at alloc.c:2960
#1 0x6b4c0 in garbage_collect_1 () at alloc.c:3109
#2 0xb3bf4 in Feval (form=9190640) at eval.c:3256
#3 0x19a3b8 in readevalloop (readcharfun=9368064, sourcename=9516676,
evalfun=0xb37f0 <Feval>, printflag=0) at lread.c:1449
#4 0x198c9c in Fload_internal (file=9516676, noerror=3153920,
nomessage=3332124, nosuffix=3332100, codesys=3456036, used_codesys=3332100)
at lread.c:737
#5 0xb4870 in Ffuncall (nargs=-1, args=0xefff77f4) at eval.c:3528
#6 0x7a34c in execute_optimized_program (
program=0x5b2c87 "+\207de-files.el\n;;; emacs version 21.2 (beta43)",
stack_depth=5, constants_data=0x5b2d10) at bytecode.c:746
#7 0x79e98 in funcall_compiled_function (fun=11, nargs=4, args=0xefff79e4)
at bytecode.c:518
#8 0xb49c4 in Ffuncall (nargs=4, args=0xefff79e0) at eval.c:3563
#9 0xb8c70 in call4 (fn=3478876, arg0=9516676, arg1=3332100, arg2=3332124,
arg3=3332100) at eval.c:4235
#10 0x13fc10 in Frequire (feature=9451884, filename=3332100) at fns.c:3347
#11 0xb47f8 in Ffuncall (nargs=2, args=0xefff7b9c) at eval.c:3528
#12 0x7a34c in execute_optimized_program (program=0x6ead3c "\207",
stack_depth=2, constants_data=0x845f10) at bytecode.c:746
#13 0x79e98 in funcall_compiled_function (fun=3, nargs=1, args=0xefff7d70)
at bytecode.c:518
#14 0xb49c4 in Ffuncall (nargs=1, args=0xefff7d6c) at eval.c:3563
#15 0x7a34c in execute_optimized_program (
program=0xefff7e0b "\210ÂÃÄÅ#\210ÂÆÇÅ#\210ÈÉÊ\"\2070\b", stack_depth=1,
constants_data=0x8cf990) at bytecode.c:746
#16 0x7e820 in Fbyte_code (instructions=-268468728, constants=9238912,
stack_depth=9) at bytecode.c:2405
#17 0xb3ffc in Feval (form=9190028) at eval.c:3331
#18 0x19a3b8 in readevalloop (readcharfun=9368576, sourcename=9476964,
evalfun=0xb37f0 <Feval>, printflag=0) at lread.c:1449
#19 0x198c9c in Fload_internal (file=9476964, noerror=3153920,
nomessage=3332124, nosuffix=3332100, codesys=3456036, used_codesys=3332100)
at lread.c:737
#20 0xb4870 in Ffuncall (nargs=-1, args=0xefff839c) at eval.c:3528
#21 0x7a34c in execute_optimized_program (
program=0x5b2c87 "+\207de-files.el\n;;; emacs version 21.2 (beta43)",
stack_depth=5, constants_data=0x5b2d10) at bytecode.c:746
#22 0x79e98 in funcall_compiled_function (fun=11, nargs=4, args=0xefff858c)
at bytecode.c:518
#23 0xb49c4 in Ffuncall (nargs=4, args=0xefff8588) at eval.c:3563
#24 0xb8c70 in call4 (fn=3478876, arg0=9476964, arg1=3332100, arg2=3332124,
arg3=3332100) at eval.c:4235
#25 0x13fc10 in Frequire (feature=9451764, filename=3332100) at fns.c:3347
#26 0xb47f8 in Ffuncall (nargs=2, args=0xefff8744) at eval.c:3528
#27 0x7a34c in execute_optimized_program (program=0x6ead3c "\207",
stack_depth=2, constants_data=0x845f10) at bytecode.c:746
#28 0x79e98 in funcall_compiled_function (fun=3, nargs=1, args=0xefff8918)
at bytecode.c:518
#29 0xb49c4 in Ffuncall (nargs=1, args=0xefff8914) at eval.c:3563
#30 0x7a34c in execute_optimized_program (
program=0xefff89fa "\210ËÀ!\210ËÎ!\210ÏÐÑ!ÀÒÓ!\030Ô\bÕ\"\210Ö\bÐÑ!\"\210×\b!Õk«\004\bª\fØÓÙÕÙ\211\211\211\211&\b)#\210ÐÑ!\207", stack_depth=1,
constants_data=0x8c6690) at bytecode.c:746
#31 0x7e820 in Fbyte_code (instructions=-268465712, constants=9201280,
stack_depth=25) at bytecode.c:2405
#32 0xb3ffc in Feval (form=9451156) at eval.c:3331
#33 0x19a3b8 in readevalloop (readcharfun=9369600, sourcename=9367332,
evalfun=0xb37f0 <Feval>, printflag=0) at lread.c:1449
#34 0x198c9c in Fload_internal (file=9367332, noerror=3153920,
nomessage=3332124, nosuffix=3332100, codesys=3456036, used_codesys=3332100)
at lread.c:737
#35 0xb4870 in Ffuncall (nargs=-1, args=0xefff9074) at eval.c:3528
#36 0x7a34c in execute_optimized_program (
program=0x5b2c87 "+\207de-files.el\n;;; emacs version 21.2 (beta43)",
stack_depth=5, constants_data=0x5b2d10) at bytecode.c:746
#37 0x79e98 in funcall_compiled_function (fun=11, nargs=4, args=0xefff9264)
at bytecode.c:518
#38 0xb49c4 in Ffuncall (nargs=4, args=0xefff9260) at eval.c:3563
#39 0xb8c70 in call4 (fn=3478876, arg0=9367332, arg1=3332100, arg2=3332124,
arg3=3332100) at eval.c:4235
#40 0x13fc10 in Frequire (feature=9451620, filename=3332100) at fns.c:3347
#41 0xb47f8 in Ffuncall (nargs=2, args=0xefff941c) at eval.c:3528
#42 0x7a34c in execute_optimized_program (program=0x6ead3c "\207",
stack_depth=2, constants_data=0x845f10) at bytecode.c:746
#43 0x79e98 in funcall_compiled_function (fun=3, nargs=1, args=0xefff95f0)
at bytecode.c:518
#44 0xb49c4 in Ffuncall (nargs=1, args=0xefff95ec) at eval.c:3563
#45 0x7a34c in execute_optimized_program (
program=0xefff96c2 "\210ª,ÂË!\210ª&ÇÌ!«\022\bÍY«\aÂÎ!\210ª\026ÂÏ!\210ª\020ÐÑ!«\aÂÒ!\210ª\005ÂË!\210ÂÁ!\210ÂÓ!\210ÔÕÖ!Á×Ø!\031Ù\tÚ\"\210Û\tÕÖ!\"\210Ü\t!Úk«\004\tª\fÝØÞÚÞ\211\211\211\211&\b)#\210ÕÖ!\207ages/lisp/apel/pces.elc",
stack_depth=1, constants_data=0x8c9810) at bytecode.c:746
#46 0x7e820 in Fbyte_code (instructions=-268462424, constants=9213952,
stack_depth=25) at bytecode.c:2405
#47 0xb3ffc in Feval (form=9450496) at eval.c:3331
#48 0x19a3b8 in readevalloop (readcharfun=9370112, sourcename=9365956,
evalfun=0xb37f0 <Feval>, printflag=0) at lread.c:1449
#49 0x198c9c in Fload_internal (file=9365956, noerror=3153920,
nomessage=3332124, nosuffix=3332100, codesys=3456036, used_codesys=3332100)
at lread.c:737
#50 0xb4870 in Ffuncall (nargs=-1, args=0xefff9db4) at eval.c:3528
#51 0x7a34c in execute_optimized_program (
program=0x5b2c87 "+\207de-files.el\n;;; emacs version 21.2 (beta43)",
stack_depth=5, constants_data=0x5b2d10) at bytecode.c:746
#52 0x79e98 in funcall_compiled_function (fun=11, nargs=4, args=0xefff9fa4)
at bytecode.c:518
#53 0xb49c4 in Ffuncall (nargs=4, args=0xefff9fa0) at eval.c:3563
#54 0xb8c70 in call4 (fn=3478876, arg0=9365956, arg1=3332100, arg2=3332124,
arg3=3332100) at eval.c:4235
#55 0x13fc10 in Frequire (feature=9336708, filename=3332100) at fns.c:3347
#56 0xb47f8 in Ffuncall (nargs=2, args=0xefffa15c) at eval.c:3528
#57 0x7a34c in execute_optimized_program (program=0x6ead3c "\207",
stack_depth=2, constants_data=0x845f10) at bytecode.c:746
#58 0x79e98 in funcall_compiled_function (fun=3, nargs=1, args=0xefffa330)
at bytecode.c:518
#59 0xb49c4 in Ffuncall (nargs=1, args=0xefffa32c) at eval.c:3563
#60 0x7a34c in execute_optimized_program (
program=0xefffa3eb "\210ÅÆ!«\035ÅÇ!«\aÃÈ!\210ª!\bÉY«\aÃÊ!\210ª\026ÃË!\210ª\020ÌÍ!«\aÃÎ!\210ª\005ÃÏ!\210ÐÑ!¬!ÑÒM\210ÑÓNÔs¬\006ÕÖÑ\"\210×ÑÓØ#\210Ñ\tB\021×ÑÙÚ#\210ÐÛ!¬!ÛÜM\210ÛÓNÔs¬\006ÕÖÛ\"\210×ÛÓØ#\210Û\tB\021×ÛÙÚ#\210ÃÂ!\210ÃÝ!\210×Þß!Âàá!\032â\nã\"\210ä\nÞß!\"\210å\n!ãk«\004\nª\fæáçãç\211\211\211\211&\b)#\210Þß!\207¼", stack_depth=1, constants_data=0x8c9910) at bytecode.c:746
#61 0x7e820 in Fbyte_code (instructions=-268459032, constants=9214208,
stack_depth=25) at bytecode.c:2405
#62 0xb3ffc in Feval (form=9449812) at eval.c:3331
#63 0x19a3b8 in readevalloop (readcharfun=9370624, sourcename=9365252,
evalfun=0xb37f0 <Feval>, printflag=0) at lread.c:1449
#64 0x198c9c in Fload_internal (file=9365252, noerror=3153920,
nomessage=3332124, nosuffix=3332100, codesys=3456036, used_codesys=3332100)
at lread.c:737
#65 0xb4870 in Ffuncall (nargs=-1, args=0xefffabac) at eval.c:3528
#66 0x7a34c in execute_optimized_program (
program=0x5b2c87 "+\207de-files.el\n;;; emacs version 21.2 (beta43)",
stack_depth=5, constants_data=0x5b2d10) at bytecode.c:746
#67 0x79e98 in funcall_compiled_function (fun=11, nargs=4, args=0xefffad9c)
at bytecode.c:518
#68 0xb49c4 in Ffuncall (nargs=4, args=0xefffad98) at eval.c:3563
#69 0xb8c70 in call4 (fn=3478876, arg0=9365252, arg1=3332100, arg2=3332124,
arg3=3332100) at eval.c:4235
#70 0x13fc10 in Frequire (feature=9336660, filename=3332100) at fns.c:3347
#71 0xb47f8 in Ffuncall (nargs=2, args=0xefffaf54) at eval.c:3528
#72 0x7a34c in execute_optimized_program (program=0x6ead3c "\207",
stack_depth=2, constants_data=0x845f10) at bytecode.c:746
#73 0x79e98 in funcall_compiled_function (fun=3, nargs=1, args=0xefffb128)
at bytecode.c:518
#74 0xb49c4 in Ffuncall (nargs=1, args=0xefffb124) at eval.c:3563
#75 0x7a34c in execute_optimized_program (
program=0xefffb306 "\210Æë!\210Æì!\207", stack_depth=1,
constants_data=0x8c9a10) at bytecode.c:746
#76 0x7e820 in Fbyte_code (instructions=-268455496, constants=9214464,
stack_depth=7) at bytecode.c:2405
#77 0xb3ffc in Feval (form=9362864) at eval.c:3331
#78 0x19a3b8 in readevalloop (readcharfun=9371136, sourcename=9364068,
evalfun=0xb37f0 <Feval>, printflag=0) at lread.c:1449
#79 0x198c9c in Fload_internal (file=9364068, noerror=3153920,
nomessage=3332124, nosuffix=3332100, codesys=3456036, used_codesys=3332100)
at lread.c:737
#80 0xb4870 in Ffuncall (nargs=-1, args=0xefffbb2c) at eval.c:3528
#81 0x7a34c in execute_optimized_program (
program=0x5b2c87 "+\207de-files.el\n;;; emacs version 21.2 (beta43)",
stack_depth=5, constants_data=0x5b2d10) at bytecode.c:746
#82 0x79e98 in funcall_compiled_function (fun=11, nargs=4, args=0xefffbd1c)
at bytecode.c:518
#83 0xb49c4 in Ffuncall (nargs=4, args=0xefffbd18) at eval.c:3563
#84 0xb8c70 in call4 (fn=3478876, arg0=9364068, arg1=3332100, arg2=3332124,
arg3=3332100) at eval.c:4235
#85 0x13fc10 in Frequire (feature=9336276, filename=3332100) at fns.c:3347
#86 0xb47f8 in Ffuncall (nargs=2, args=0xefffbed4) at eval.c:3528
#87 0x7a34c in execute_optimized_program (program=0x6ead3c "\207",
stack_depth=2, constants_data=0x845f10) at bytecode.c:746
#88 0x79e98 in funcall_compiled_function (fun=3, nargs=1, args=0xefffc0a8)
at bytecode.c:518
#89 0xb49c4 in Ffuncall (nargs=1, args=0xefffc0a4) at eval.c:3563
#90 0x7a34c in execute_optimized_program (program=0xefffc13b "\210ÀÂ!\207",
stack_depth=1, constants_data=0x8cd330) at bytecode.c:746
#91 0x7e820 in Fbyte_code (instructions=-268451528, constants=9229088,
stack_depth=5) at bytecode.c:2405
#92 0xb3ffc in Feval (form=9362252) at eval.c:3331
#93 0x19a3b8 in readevalloop (readcharfun=9367552, sourcename=9312292,
evalfun=0xb37f0 <Feval>, printflag=0) at lread.c:1449
#94 0x198c9c in Fload_internal (file=9312292, noerror=3153920,
nomessage=3332124, nosuffix=3332100, codesys=3456036, used_codesys=3332100)
at lread.c:737
#95 0xb4870 in Ffuncall (nargs=-1, args=0xefffc69c) at eval.c:3528
#96 0x7a34c in execute_optimized_program (
program=0x5b2c87 "+\207de-files.el\n;;; emacs version 21.2 (beta43)",
stack_depth=5, constants_data=0x5b2d10) at bytecode.c:746
#97 0x79e98 in funcall_compiled_function (fun=11, nargs=4, args=0xefffc88c)
at bytecode.c:518
#98 0xb49c4 in Ffuncall (nargs=4, args=0xefffc888) at eval.c:3563
#99 0xb8c70 in call4 (fn=3478876, arg0=9312292, arg1=3332100, arg2=3332124,
arg3=3332100) at eval.c:4235
#100 0x13fc10 in Frequire (feature=9335844, filename=3332100) at fns.c:3347
#101 0xb47f8 in Ffuncall (nargs=2, args=0xefffca44) at eval.c:3528
#102 0x7a34c in execute_optimized_program (program=0x6ead3c "\207",
stack_depth=2, constants_data=0x845f10) at bytecode.c:746
#103 0x79e98 in funcall_compiled_function (fun=3, nargs=1, args=0xefffcc18)
at bytecode.c:518
#104 0xb49c4 in Ffuncall (nargs=1, args=0xefffcc14) at eval.c:3563
#105 0x7a34c in execute_optimized_program (
program=0xefffccab "\210ÆÈ!\210ÆÉ!\210ÆÊ!\210ÆË!\210ÆÌ!\210ÆÍ!\210ÆÎ!\210ÆÏ!\210ÆÐ!\210Ä\rB\025Ñ\024Ã\rB\025Ò\f!\023Â\rB\025\013\022Á\rB\025ÓÁ!¬\003Ô\021À\rB\025ÓÀ!¬\003Õ\020Ö\rB\025ÓÖ!¬\004×\026\026Ø\rB\025ÓØ!¬\004Ù\026\030Ú\rB\025ÓÚ!¬\004Û\026\032Ü\rB\025ÓÜ!¬\004Ý\026\034Æ\207", stack_depth=1,
constants_data=0x8c9b10) at bytecode.c:746
#106 0x7e820 in Fbyte_code (instructions=-268448600, constants=9214720,
stack_depth=5) at bytecode.c:2405
#107 0xb3ffc in Feval (form=9311340) at eval.c:3331
#108 0x19a3b8 in readevalloop (readcharfun=9258496, sourcename=9338164,
evalfun=0xb37f0 <Feval>, printflag=0) at lread.c:1449
#109 0x198c9c in Fload_internal (file=9338164, noerror=3153920,
nomessage=3332124, nosuffix=3332100, codesys=3456036, used_codesys=3332100)
at lread.c:737
#110 0xb4870 in Ffuncall (nargs=-1, args=0xefffd38c) at eval.c:3528
#111 0x7a34c in execute_optimized_program (
program=0x5b2c87 "+\207de-files.el\n;;; emacs version 21.2 (beta43)",
stack_depth=5, constants_data=0x5b2d10) at bytecode.c:746
#112 0x79e98 in funcall_compiled_function (fun=11, nargs=4, args=0xefffd57c)
at bytecode.c:518
#113 0xb49c4 in Ffuncall (nargs=4, args=0xefffd578) at eval.c:3563
#114 0xb8c70 in call4 (fn=3478876, arg0=9338164, arg1=3332100, arg2=3332124,
arg3=3332100) at eval.c:4235
#115 0x13fc10 in Frequire (feature=9335676, filename=3332100) at fns.c:3347
#116 0xb47f8 in Ffuncall (nargs=2, args=0xefffd734) at eval.c:3528
#117 0x7a34c in execute_optimized_program (program=0x6ead3c "\207",
stack_depth=2, constants_data=0x845f10) at bytecode.c:746
#118 0x79e98 in funcall_compiled_function (fun=3, nargs=1, args=0xefffd908)
at bytecode.c:518
#119 0xb49c4 in Ffuncall (nargs=1, args=0xefffd904) at eval.c:3563
#120 0x7a34c in execute_optimized_program (
program=0xefffd99b "\210Â\013B\023Æ\022Á\013B\023ÇÁ!¬\003Æ\021À\013B\023ÇÀ!¬\003È\020Ä\207B", stack_depth=1, constants_data=0x8cf9d0) at bytecode.c:746
#121 0x7e820 in Fbyte_code (instructions=-268445288, constants=9238976,
stack_depth=5) at bytecode.c:2405
#122 0xb3ffc in Feval (form=6203600) at eval.c:3331
#123 0x19a3b8 in readevalloop (readcharfun=9257472, sourcename=6894868,
evalfun=0xb37f0 <Feval>, printflag=0) at lread.c:1449
#124 0x198c9c in Fload_internal (file=6894868, noerror=3153920,
nomessage=3332100, nosuffix=3332100, codesys=3456036, used_codesys=3332100)
at lread.c:737
#125 0xb4870 in Ffuncall (nargs=-1, args=0xefffdf4c) at eval.c:3528
#126 0x7a34c in execute_optimized_program (
program=0x5b2c87 "+\207de-files.el\n;;; emacs version 21.2 (beta43)",
stack_depth=5, constants_data=0x5b2d10) at bytecode.c:746
#127 0x79e98 in funcall_compiled_function (fun=11, nargs=4, args=0xefffe13c)
at bytecode.c:518
#128 0xb49c4 in Ffuncall (nargs=4, args=0xefffe138) at eval.c:3563
#129 0xb8c70 in call4 (fn=3478876, arg0=6894868, arg1=3332100, arg2=3332100,
arg3=3332100) at eval.c:4235
#130 0xb3650 in do_autoload (fundef=6776528, funname=5783092) at eval.c:3146
#131 0xb310c in Fcommand_execute (cmd=5783092, record_flag=3332124,
keys=3332100) at eval.c:2955
#132 0xb4810 in Ffuncall (nargs=-1, args=0xefffe3bc) at eval.c:3528
#133 0x7a34c in execute_optimized_program (
program=0x76b251 "\210\0138\b¬\023Ñ Ò a«\aÓ pa«\006Ô \210ª\004Õ \210Ö×!\eØÙË\013A«\004Úª\002Û\nÜ\013!#\"\210Ö\016\036!\210ÝÙ!*\207Ï\fÐ\"\207 ",
stack_depth=2, constants_data=0x457710) at bytecode.c:746
#134 0x79e98 in funcall_compiled_function (fun=7, nargs=1, args=0xefffe59c)
at bytecode.c:518
#135 0xb49c4 in Ffuncall (nargs=1, args=0xefffe598) at eval.c:3563
#136 0x80f68 in Fcall_interactively (function=4534348, record_flag=3332100,
keys=3332100) at callint.c:940
#137 0xb3194 in Fcommand_execute (cmd=4534348, record_flag=3332100,
keys=3332100) at eval.c:2970
#138 0x111424 in execute_command_event (command_builder=0x6b9f80,
event=8945244) at event-stream.c:3834
#139 0x111e44 in Fdispatch_event (event=7390000) at event-stream.c:4117
#140 0x8c194 in Fcommand_loop_1 () at cmdloop.c:583
#141 0x8c42c in command_loop_1 (dummy=5074816) at cmdloop.c:494
#142 0xb0434 in condition_case_1 (handlers=3107244,
bfun=0x8c3e0 <command_loop_1>, barg=3332100, hfun=0x8c48c <cmd_error>,
harg=3332100) at eval.c:1651
#143 0x8c59c in command_loop_2 (dummy=3332100) at cmdloop.c:256
#144 0xb92d4 in internal_catch (tag=3412428, func=0x8c550 <command_loop_2>,
arg=3332100, threw=0x0) at eval.c:1317
#145 0x8b8ac in initial_command_loop (load_me=3332100) at cmdloop.c:305
#146 0xabd58 in sort_args (argc=2628608, argv=0xefffedf4) at emacs.c:2253
(gdb) quit
The program is running. Exit anyway? (y or n) y
Recent keystrokes:
misc-user
Recent messages (most recent first):
Parsing /home/alt/.mailrc...
Loading mail-abbrevs...done
Loading mail-abbrevs...
Loading emacsbug...done
Loading emacsbug...
- 1 participants
- 0 comments