GPLv3|L8R -- Status report - ready for inspection?
7 years, 6 months
Mats Lidell
Mats Lidell
Hi,
Here comes yet another status report from the project of converting to
GPLv3 or later.
There are two lists of files below. The first list contains all files
that are in an undecided state. Please inspect: Do we need to do anything
with them. If so what?
The second list contains all files that we can leave untouched and the
reason for that. Please inspect: Are all reasons OK and correct?
Are we getting close to the were an inspection of the xemacs-gplv3
repository could be performed? With the intent that it that is OK we
could merge back to trunk and go GPLv3 or later?
----------------------------------------------------------------------
"CHANGES-beta"
"ChangeLog"
"PROBLEMS"
"README"
"README.GPLv3"
"etc/ChangeLog"
"etc/Emacs.ad"
"etc/InstallGuide"
"etc/NEWS"
"etc/ONEWS"
"etc/OONEWS"
"etc/README"
"etc/editclient.sh"
"etc/emacskeys.sco"
"etc/emacsstrs.sco"
"etc/gtkrc"
"etc/package-index.LATEST.gpg"
"etc/sample.Xresources"
"etc/xemacs.1"
"lib-src/ChangeLog"
"lib-src/README"
"lisp/ChangeLog"
"lisp/README"
"lisp/mule/mule-locale.txt"
"man/ChangeLog"
"man/README"
"modules/ChangeLog"
"modules/base64/Makefile"
"modules/common/configure-post.ac"
"modules/common/configure-pre.ac"
"modules/zlib/Makefile"
"nt/ChangeLog"
"nt/Emacs.ad.h"
"nt/Installation.el"
"nt/README"
"nt/Win32.cf"
"nt/lisp.ico"
"nt/site.def"
"nt/xemacs.dsp"
"nt/xemacs.dsw"
"src/ChangeLog"
"src/README"
"src/README.kkcc"
"src/m/README"
"src/s/README"
"src/s/freebsd.h"
"src/s/irix6-0.h"
"src/s/netbsd.h"
"src/s/sol2.h"
"tests/ChangeLog"
"tests/Dnd/README"
"tests/automated/README"
"version.sh.in"
----------------------------------------------------------------------
These files below are the files that we might be able to leave as
they are. The reason for why they need not to be changed is listed
after each file: (Some reasons are taken verbatim from private
communication or the "GPL version 3 source survey")
----------------------------------------------------------------------
"INSTALL" -> old FSF Documentation license
"config.guess" -> Part of config which is still GPLv2 or later. See "http://savannah.gnu.org/projects/config"
"config.sub" -> Part of config which is still GPLv2 or later. See "http://savannah.gnu.org/projects/config"
"etc/ETAGS.ChangeLog" -> BSD and GPL v2 or later
"etc/VEGETABLES" -> Not copyrightable.
"etc/XKeysymDB" -> MIT
"etc/ctags.1" -> Part of the etags distribution, which is not part of XEmacs.
"etc/custom/example-themes/ex-custom-file" -> Generated(!?) or GPL V2 or later?
"etc/etags.1" -> Part of the etags distribution, which is not part of XEmacs.
"etc/gnuattach.1" -> simple man link to gnuserv.1
"etc/gnuclient.1" -> simple man link to gnuserv.1
"etc/gnudoit.1" -> simple man link to gnuserv.1
"etc/refcard.ps.gz" -> Generated from refcard..tex
"etc/sample.Xdefaults" -> It is deprecated, so it can be removed but is only a three line reference to .Xresources
"etc/xemacs-X.ico" -> GPLv2 or later but there is not meta data for the file where this can be documented.
"info/dir" -> Generated(?)
"install-sh" -> MIT-style "no advertising" license
"lib-src/b2m.c" -> This is the version from GNU Emacs, so should be OK.
"lib-src/config.values.in" -> Generated.
"lib-src/emacs.csh" -> I don't think this even works with XEmacs ("emacsclient"), so I believe we can just delete it.
"lib-src/insert-data-in-exec.c" -> Compatible license.
"lib-src/mmencode.c" -> Compatible license.
"lisp/dump-paths.el" -> Empty file. Not copyrightable.
"lisp/term/bobcat.el" -> Emacs version has no explicit license declaration
"lisp/term/vt102.el" -> Emacs version has no explicit license declaration
"lisp/term/vt125.el" -> Emacs version has no explicit license declaration
"lisp/term/vt200.el" -> Emacs version has no explicit license declaration
"lisp/term/vt201.el" -> Emacs version has no explicit license declaration
"lisp/term/vt220.el" -> Emacs version has no explicit license declaration
"lisp/term/vt240.el" -> Emacs version has no explicit license declaration
"lisp/term/vt300.el" -> Emacs version has no explicit license declaration
"lisp/term/vt320.el" -> Emacs version has no explicit license declaration
"lisp/term/vt400.el" -> Emacs version has no explicit license declaration
"lisp/term/vt420.el" -> Emacs version has no explicit license declaration
"lock/.precious" -> Not copyrightable.
"modules/canna/install-sh" -> MIT
"modules/ldap/install-sh" -> MIT
"modules/postgresql/install-sh" -> MIT
"modules/sample/external/install-sh" -> MIT
"modules/sample/internal/install-sh" -> MIT
"move-if-change" -> Identical to GPLv3 or later Emacs version
"nt/Xmd.patch" -> GPLv2 or later but only a few lines
"nt/file.ico" -> MIT
"nt/minitar.c" -> Public domain
"nt/paths.h" -> Generated
"nt/xemacs.ico" -> GPLv2 or later but there is not meta data for the file where this can be documented.
"src/alloca.c" -> Public domain.
"src/depend" -> Generated
"src/emacs-marshals.c" -> Generated.
"src/emacs-widget-accessors.c" -> Generated.
"src/intl-auto-encap-win32.c" -> Generated.
"src/intl-auto-encap-win32.h" -> Generated.
"src/libsst.c" -> Compatible license.
"src/libsst.h" -> Compatible license.
"src/libst.h" -> Compatible copyright.
"src/linuxplay.c" -> Compatible license. (MIT-like)
"src/miscplay.c" -> Compatible license. (MIT-like)
"src/miscplay.h" -> Compatible license. (MIT-like)
"src/nas.c" -> Compatible license. (MIT-like)
"src/paths.h.in" -> Generated.
"src/s/openbsd.h" -> Too short. (< 10 lines)
"src/s/usg5-4-2.h" -> Too short. (< 10 lines)
"src/sunplay.c" -> Compatible copyright.
"tests/gtk/UNIMPLEMENTED" -> Does notes need a license?
"tests/tooltalk/beeps.el" -> Too short. (< 10 lines)
----------------------------------------------------------------------
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 4 participants
- 3 comments
Crash running Cygwin bash shell under XEmacs
12 years, 3 months
Mike Alexander
Mike Alexander
I had a need to run something on my Windows machine today which
required a newer version of Cygwin than the ancient one that was
installed there. After I upgraded to the current version (1.7.9) I
can't start a shell in XEmacs (via M-X shell) using Cygwin's version of
bash. When I try to do so I get
Process bash.exe exited abnormally with code 35584
3 [sig] bash 1168 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
1556 [sig] bash 1168 open_stackdumpfile: Dumping stack trace to
bash.exe.stackdump
The stack dump is uninteresting except that the crash happens at offset
0x169220 in cygwin1.dll. It appears that this crash happens very early
on, before it's read /etc/profile. I see that I also have similar
stack dumps from other programs (find.exe and xargs.exe) in the XEmacs
directory all exactly the same.
I installed the latest Windows version of XEmacs from the installer at
<http://ftp.xemacs.org/pub/xemacs/binaries/win32/InnoSetup/XEmacs_Setup_21...>
and tried starting it with --vanilla. This didn't make any difference.
I also did a clean install of Cygwin 1.7.9 in case there was any crud
left around from the old version. This also didn't help. I'm running
on an old Dell with Windows XP Professional SP3. Perhaps that's the
problem. I probably should install Windows on my Mac under one of the
emulators, but that's more than I want to get into right now.
I've Googled around a bit and although others have seen this problem,
none of the solutions (mostly involving changing ownership of Cygwin
files and running rebaseall) did any good. The bash shell runs fine
when I start it using the .bat file installed by Cygwin, so it's
basically working, but it won't run in an XEmacs shell window.
Has anyone else seen this or know how to fix it? This little episode
reminds me why I avoid using Windows, but sometimes it's necessary.
Mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 5 participants
- 5 comments
symbol's value as variable is void: allow-remote-paths
12 years, 11 months
Richard Cook
Richard Cook
Hi, I compiled xemacs myself and installed into $HOME/xemacs-without-ipv6-cname
I then made a symlink of $HOME/xemacs-without-ipv6-cname/bin/xemacs to $HOME/bin/xemacs
I untarred the sumo tarball from http://ftp.xemacs.org/pub/xemacs/packages/xemacs-sumo-2009-02-17.tar.gz and untarred it into $HOME/xemacs-without-ipv6-cname/lib/xemacs, which made a directory called xemacs-packages there.
When I run xemacs, I am not able to update my packages.
I go to Tools -> Packages -> Set Download Site -> Official Releases -> US and choose US Main.
I then go "update package index" or any other command in the Tools menu about Packages and it complains: "symbol's value as variable is void: allow-remote-paths"
Can anyone help me with this? Thanks.
--
✐Richard Cook
✇ Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557
7000 East Avenue, Livermore, CA, 94550, USA
☎ (office) (925) 423-9605
☎ (fax) (925) 423-6961
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/mailman/listinfo/xemacs-beta
- 12 participants
- 51 comments
MacOS X Lion segv (signal 11), using MacPorts (install from scratch)
13 years
Nelson Ferreira
Nelson Ferreira
Hi all,
Has anyone else managed to successfully build XEmacs 21.5 under MacOS X
Lion ?
(PS: I did this following similar crash with SXEmacs, so I suspect some
bad influence of Lion on pdump...)
I am seeing a crash at make:
./xemacs -no-packages -batch -no-autoloads -l update-elc-2.el -f batch-update-elc-2 /Users/njsf/Projects/XEmacs/xemacs-beta/src/../lisp
make[1]: *** [update-elc-2] Segmentation fault: 11
make: *** [src] Error 2
The crash reporter gives the following information:
Process: xemacs [66766]
Path: /Users/USER/*/xemacs
Identifier: xemacs
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: gnumake [66169]
Date/Time: 2011-09-13 21:46:05.466 -0400
OS Version: Mac OS X 10.7.1 (11B26)
Report Version: 9
Interval Since Last Report: 110318 sec
Crashes Since Last Report: 1
Per-App Crashes Since Last Report: 1
Anonymous UUID: E1FEAF32-402E-42B6-B6C7-B8DB1512C1D0
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000010f1f1a10
VM Regions Near 0x10f1f1a10:
MALLOC guard page 000000010d53c000-000000010d53d000 [ 4K] ---/rwx SM=NUL
-->
MALLOC_TINY 00007f911b400000-00007f911b411000 [ 68K] rw-/rwx SM=COW
Application Specific Information:
objc[66766]: garbage collection is OFF
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 xemacs 0x000000010c658f80 pdump_load_finish + 624 (dumper.c:2336)
1 xemacs 0x000000010c65959b pdump_load + 33 (dumper.c:2683)
2 xemacs 0x000000010c624178 xemacs_21_5_b31_i386_apple_darwin11_1_0 + 3367 (emacs.c:1407)
3 xemacs 0x000000010c625690 main + 152 (emacs.c:3192)
4 xemacs 0x000000010c5c119c start + 52
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x000000010f1f1a10 rbx: 0x0000000000000009 rcx: 0x0000000000369b48 rdx: 0x000000010cc49b48
rdi: 0x000000010c8e0008 rsi: 0x000000010c84fc9c rbp: 0x00007fff6c1bf7a0 rsp: 0x00007fff6c1bf6e0
r8: 0x000000004e70075c r9: 0x00007fff6c1bf8d8 r10: 0x0000000000098000 r11: 0x00007fff95258ec0
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x000000010c658f80 rfl: 0x0000000000010202 cr2: 0x000000010f1f1a10
Logical CPU: 1
Binary Images:
0x10c5c0000 - 0x10c8c3ff7 +xemacs (??? - ???) <8EEB0246-E825-3412-ADFA-4D48CC4C0157> /Users/USER/*/xemacs
0x10cffd000 - 0x10d04bff7 +libXaw.7.dylib (8.0.0 - compatibility 8.0.0) <AAFC320F-C6C8-37D2-9ACD-2CB9EB2A0BFE> /opt/local/lib/libXaw.7.dylib
0x10d06d000 - 0x10d0c4ff7 +libtiff.3.dylib (13.5.0 - compatibility 13.0.0) <D371F602-5352-390B-97A7-F260DF3151A9> /opt/local/lib/libtiff.3.dylib
0x10d0d1000 - 0x10d105ff7 +libjpeg.8.dylib (12.0.0 - compatibility 12.0.0) <547B0670-CCE5-315A-BECC-E3F818C76388> /opt/local/lib/libjpeg.8.dylib
0x10d10c000 - 0x10d120fff +libz.1.dylib (1.2.5 - compatibility 1.0.0) <B6C19687-AAE1-37CB-BA87-0426C2A833E0> /opt/local/lib/libz.1.dylib
0x10d127000 - 0x10d129ff7 +libcompface.0.dylib (1.5.2 - compatibility 1.5.2) <BCD91461-F4C1-382C-8039-0FE51937D8E2> /opt/local/lib/libcompface.0.dylib
0x10d13d000 - 0x10d14afff +libXpm.4.dylib (16.0.0 - compatibility 16.0.0) <E5E6977D-EE43-3F31-944F-AE3344269818> /opt/local/lib/libXpm.4.dylib
0x10d150000 - 0x10d162fff +libXmu.6.dylib (9.0.0 - compatibility 9.0.0) <F585D672-702A-3C5E-A6E9-86FBBBB8020E> /opt/local/lib/libXmu.6.dylib
0x10d16b000 - 0x10d1b1fff +libXt.6.dylib (7.0.0 - compatibility 7.0.0) <DA9EB881-3DC7-3FF2-84D2-B17721560EA8> /opt/local/lib/libXt.6.dylib
0x10d1cd000 - 0x10d1daff7 +libXext.6.dylib (11.0.0 - compatibility 11.0.0) <F8FA5759-7C9D-3B4C-AA8F-6340A4110E7D> /opt/local/lib/libXext.6.dylib
0x10d1e5000 - 0x10d2f8fff +libX11.6.dylib (10.0.0 - compatibility 10.0.0) <32ADB232-24AC-374A-9CAD-BCB19D5E5B1C> /opt/local/lib/libX11.6.dylib
0x10d322000 - 0x10d327ff7 +libSM.6.dylib (7.1.0 - compatibility 7.0.0) <D60FB83A-8F6F-3879-A4E8-AA20A186247A> /opt/local/lib/libSM.6.dylib
0x10d32d000 - 0x10d33dff7 +libICE.6.dylib (10.0.0 - compatibility 10.0.0) <77070DB2-3B37-3833-B36B-BEC1F951AE78> /opt/local/lib/libICE.6.dylib
0x10d34a000 - 0x10d34efff +libgdbm.4.dylib (5.0.0 - compatibility 5.0.0) <F8B0FEEE-C653-3D75-AC68-ABDE1FB9C18C> /opt/local/lib/libgdbm.4.dylib
0x10d353000 - 0x10d390ff7 +libncurses.5.dylib (5.0.0 - compatibility 5.0.0) <60014346-C481-3C60-A269-47B991D13365> /opt/local/lib/libncurses.5.dylib
0x10d3a1000 - 0x10d3b4fe7 +libgcc_s.1.dylib (??? - ???) <E47C20F0-4019-3A3F-8C72-5E4DAA23C068> /opt/local/lib/*/libgcc_s.1.dylib
0x10d3ca000 - 0x10d3d2ff7 +libintl.8.dylib (10.1.0 - compatibility 10.0.0) <6A83574D-729E-3620-9110-E60286FCC16E> /opt/local/lib/libintl.8.dylib
0x10d3d9000 - 0x10d4d1ff7 +libiconv.2.dylib (8.1.0 - compatibility 8.0.0) <AAFF2D74-8A41-3C2F-959F-596829FF5892> /opt/local/lib/libiconv.2.dylib
0x10d4e5000 - 0x10d4f7ff7 +libxcb.1.dylib (3.0.0 - compatibility 3.0.0) <3E865F0D-7436-3AE6-98EC-D3D62739B582> /opt/local/lib/libxcb.1.dylib
0x10d505000 - 0x10d506ff7 +libXau.6.dylib (7.0.0 - compatibility 7.0.0) <3F48CAF4-6DEC-3935-ADC4-67733BCFAE1F> /opt/local/lib/libXau.6.dylib
0x10d509000 - 0x10d50cfff +libXdmcp.6.dylib (7.0.0 - compatibility 7.0.0) <73C33B9B-EF3A-3C2D-B79B-4C64AD5AA99D> /opt/local/lib/libXdmcp.6.dylib
0x7fff6c1c0000 - 0x7fff6c1f4ac7 dyld (195.5 - ???) <4A6E2B28-C7A2-3528-ADB7-4076B9836041> /usr/lib/dyld
0x7fff8b19d000 - 0x7fff8b1bdfff libsystem_kernel.dylib (1699.22.73 - compatibility 1.0.0) <69F2F501-72D8-3B3B-8357-F4418B3E1348> /usr/lib/system/libsystem_kernel.dylib
0x7fff8bc3e000 - 0x7fff8bc44fff libmacho.dylib (800.0.0 - compatibility 1.0.0) <D86F63EC-D2BD-32E0-8955-08B5EAFAD2CC> /usr/lib/system/libmacho.dylib
0x7fff8bc45000 - 0x7fff8bc4fff7 liblaunch.dylib (392.18.0 - compatibility 1.0.0) <39EF04F2-7F0C-3435-B785-BF283727FFBD> /usr/lib/system/liblaunch.dylib
0x7fff8c98e000 - 0x7fff8c997fff libnotify.dylib (80.0.0 - compatibility 1.0.0) <BD08553D-8088-38A8-8007-CF5C0B8F0404> /usr/lib/system/libnotify.dylib
0x7fff8ca4b000 - 0x7fff8ca4cff7 libremovefile.dylib (21.0.0 - compatibility 1.0.0) <C6C49FB7-1892-32E4-86B5-25AD165131AA> /usr/lib/system/libremovefile.dylib
0x7fff8cbb9000 - 0x7fff8cbbafff libdnsinfo.dylib (395.6.0 - compatibility 1.0.0) <718A135F-6349-354A-85D5-430B128EFD57> /usr/lib/system/libdnsinfo.dylib
0x7fff8ce57000 - 0x7fff8ce65fff libdispatch.dylib (187.5.0 - compatibility 1.0.0) <698F8EFB-7075-3111-94E3-891156C88172> /usr/lib/system/libdispatch.dylib
0x7fff8cec2000 - 0x7fff8cec9fff libcopyfile.dylib (85.1.0 - compatibility 1.0.0) <172B1985-F24A-34E9-8D8B-A2403C9A0399> /usr/lib/system/libcopyfile.dylib
0x7fff8d2d7000 - 0x7fff8d313fff libsystem_info.dylib (??? - ???) <BC49C624-1DAB-3A37-890F-6EFD46538424> /usr/lib/system/libsystem_info.dylib
0x7fff8d69a000 - 0x7fff8d6c7fe7 libSystem.B.dylib (159.0.0 - compatibility 1.0.0) <7B4D685D-939C-3ABE-8780-77A1889E0DE9> /usr/lib/libSystem.B.dylib
0x7fff8db7a000 - 0x7fff8db7cfff libquarantine.dylib (36.0.0 - compatibility 1.0.0) <4C3BFBC7-E592-3939-B376-1C2E2D7C5389> /usr/lib/system/libquarantine.dylib
0x7fff8e5cc000 - 0x7fff8e5d0fff libmathCommon.A.dylib (2026.0.0 - compatibility 1.0.0) <FF83AFF7-42B2-306E-90AF-D539C51A4542> /usr/lib/system/libmathCommon.A.dylib
0x7fff8e810000 - 0x7fff8e85eff7 libauto.dylib (??? - ???) <F0004B88-CA01-37D0-A77F-6651C4EC7D8E> /usr/lib/libauto.dylib
0x7fff8e85f000 - 0x7fff8e86aff7 libc++abi.dylib (14.0.0 - compatibility 1.0.0) <8FF3D766-D678-36F6-84AC-423C878E6D14> /usr/lib/libc++abi.dylib
0x7fff8ff60000 - 0x7fff90162fff libicucore.A.dylib (46.1.0 - compatibility 1.0.0) <82DCB94B-3819-3CC3-BC16-2AACA7F64F8A> /usr/lib/libicucore.A.dylib
0x7fff90163000 - 0x7fff90167fff libdyld.dylib (195.5.0 - compatibility 1.0.0) <F1903B7A-D3FF-3390-909A-B24E09BAD1A5> /usr/lib/system/libdyld.dylib
0x7fff90276000 - 0x7fff9027bfff libcache.dylib (47.0.0 - compatibility 1.0.0) <B7757E2E-5A7D-362E-AB71-785FE79E1527> /usr/lib/system/libcache.dylib
0x7fff9059d000 - 0x7fff905afff7 libz.1.dylib (1.2.5 - compatibility 1.0.0) <30CBEF15-4978-3DED-8629-7109880A19D4> /usr/lib/libz.1.dylib
0x7fff90fb1000 - 0x7fff90fb6ff7 libsystem_network.dylib (??? - ???) <4ABCEEF3-A3F9-3E06-9682-CE00F17138B7> /usr/lib/system/libsystem_network.dylib
0x7fff90fb7000 - 0x7fff90fd4ff7 libxpc.dylib (77.16.0 - compatibility 1.0.0) <0A4B4775-29A9-30D6-956B-3BE1DBF98090> /usr/lib/system/libxpc.dylib
0x7fff92240000 - 0x7fff92248fff libsystem_dnssd.dylib (??? - ???) <7749128E-D0C5-3832-861C-BC9913F774FA> /usr/lib/system/libsystem_dnssd.dylib
0x7fff92a87000 - 0x7fff92c5aff7 com.apple.CoreFoundation (6.7 - 635) <57446B22-0778-3E07-9690-96AC705D57E8> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff92cbe000 - 0x7fff92cbffff libDiagnosticMessagesClient.dylib (??? - ???) <3DCF577B-F126-302B-BCE2-4DB9A95B8598> /usr/lib/libDiagnosticMessagesClient.dylib
0x7fff92d07000 - 0x7fff92d0dff7 libunwind.dylib (30.0.0 - compatibility 1.0.0) <1E9C6C8C-CBE8-3F4B-A5B5-E03E3AB53231> /usr/lib/system/libunwind.dylib
0x7fff937de000 - 0x7fff937defff libkeymgr.dylib (23.0.0 - compatibility 1.0.0) <61EFED6A-A407-301E-B454-CD18314F0075> /usr/lib/system/libkeymgr.dylib
0x7fff93b10000 - 0x7fff93b85ff7 libc++.1.dylib (19.0.0 - compatibility 1.0.0) <C0EFFF1B-0FEB-3F99-BE54-506B35B555A9> /usr/lib/libc++.1.dylib
0x7fff94d2a000 - 0x7fff94d2bfff libsystem_sandbox.dylib (??? - ???) <8D14139B-B671-35F4-9E5A-023B4C523C38> /usr/lib/system/libsystem_sandbox.dylib
0x7fff951be000 - 0x7fff9529bfef libsystem_c.dylib (763.11.0 - compatibility 1.0.0) <1D61CA57-3C6D-30F7-89CB-CC6F0787B1DC> /usr/lib/system/libsystem_c.dylib
0x7fff952f0000 - 0x7fff95363fff libstdc++.6.dylib (52.0.0 - compatibility 7.0.0) <6BDD43E4-A4B1-379E-9ED5-8C713653DFF2> /usr/lib/libstdc++.6.dylib
0x7fff95a61000 - 0x7fff95a62ff7 libsystem_blocks.dylib (53.0.0 - compatibility 1.0.0) <8BCA214A-8992-34B2-A8B9-B74DEACA1869> /usr/lib/system/libsystem_blocks.dylib
0x7fff95b8a000 - 0x7fff95b8bfff libunc.dylib (24.0.0 - compatibility 1.0.0) <C67B3B14-866C-314F-87FF-8025BEC2CAAC> /usr/lib/system/libunc.dylib
0x7fff95eea000 - 0x7fff95f2cff7 libcommonCrypto.dylib (55010.0.0 - compatibility 1.0.0) <A5B9778E-11C3-3F61-B740-1F2114E967FB> /usr/lib/system/libcommonCrypto.dylib
0x7fff95f2d000 - 0x7fff95f32fff libcompiler_rt.dylib (6.0.0 - compatibility 1.0.0) <98ECD5F6-E85C-32A5-98CD-8911230CB66A> /usr/lib/system/libcompiler_rt.dylib
0x7fff96773000 - 0x7fff96857def libobjc.A.dylib (228.0.0 - compatibility 1.0.0) <C5F2392D-B481-3A9D-91BE-3D039FFF4DEC> /usr/lib/libobjc.A.dylib
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 32043
thread_create: 1
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=64.4M resident=17.9M(28%) swapped_out_or_unallocated=46.5M(72%)
Writable regions: Total=74.8M written=248K(0%) resident=352K(0%) swapped_out=0K(0%) unallocated=74.5M(100%)
REGION TYPE VIRTUAL
=========== =======
MALLOC 9396K
MALLOC guard page 16K
STACK GUARD 4K
Stack 64.0M
__DATA 7368K
__LINKEDIT 48.9M
__TEXT 15.6M
__UNICODE 544K
shared memory 12K
=========== =======
TOTAL 145.4M
Model: Macmini2,1, BootROM MM21.009A.B00, 2 processors, Intel Core 2 Duo, 1.83 GHz, 4 GB, SMC 1.19f2
Graphics: Intel GMA 950, GMA 950, Built-In, spdisplays_integrated_vram
Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz, 0x7F7F7F94FFFFFFFF, 0x393731353539410000000000000000000000
Memory Module: BANK 1/DIMM1, 2 GB, DDR2 SDRAM, 667 MHz, 0x7F7F7F94FFFFFFFF, 0x393731353539410000000000000000000000
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x86), Atheros 5424: 2.1.14.9
Bluetooth: Version 2.5.0f17, 2 service, 12 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Network Service: AirPort, AirPort, en1
Serial ATA Device: ST9750420AS, 750.16 GB
Parallel ATA Device: MATSHITACD-RW CW-8124
USB Device: iPod, apple_vendor_id, 0x129e, 0xfd100000 / 2
USB Device: USB2.0 Hub, 0x05e3 (Genesys Logic, Inc.), 0x0608, 0xfd300000 / 3
USB Device: Android Phone, 0x0bb4 (HTC Corporation), 0x0ff9, 0xfd330000 / 4
USB Device: USB2.0 Hub, 0x05e3 (Genesys Logic, Inc.), 0x0608, 0xfd340000 / 5
USB Device: hub_device, 0x0557 (ATEN International Co. Ltd.), 0x7000, 0x5d100000 / 2
USB Device: Trackball, 0x046d (Logitech Inc.), 0xc404, 0x5d140000 / 4
USB Device: ThinkPad USB Keyboard with TrackPoint, 0x17ef (Lenovo), 0x6009, 0x5d110000 / 3
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8205, 0x7d100000 / 2
USB Device: IR Receiver, apple_vendor_id, 0x8240, 0x7d200000 / 3
FireWire Device: WD10TPVT-00HT5T1, DMI, 400mbit_speed
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 5 participants
- 7 comments
[Bug: 21.5-b29] customize: Set Save Done button disappeared
13 years, 1 month
Stephen J. Turnbull
Stephen J. Turnbull
Uwe Brauer writes:
> Maybe I did not compile 21.5.29 correctly:
I think this may be a long-standing bug in XEmacs Customize. You need
to specify --with-widgets=$TOOLKIT in order to get display of the
buttons that are implemented as native button widgets.
> but when I try to use customize-option, say the Set Save and Done
> button, which I see in 21.4.22 are not there, (the reset button is)
> and therefore I cannot make any changes.
As a workaround, you can still use the [State] "button":
> ,----
> | This is a customization buffer.
> | Type RET or click button2 on an active field to invoke its action.
> | Invoke [Help] for more information.
> |
> | Operate on everything in this buffer:
> | reset
> |
> | Reftex Include File Commands: *
> | [INS] [DEL] String: include
> | [INS] [DEL] String: input
> | [INS] [DEL] String: subfile
> | [INS]
> | [State]: this option has been set and saved.
A
|
right here
To invoke it you TAB to it then use RET to display an action menu.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 3 participants
- 5 comments
Re: subr.el (21.5.31) for 21.5.29
13 years, 2 months
Aidan Kehoe
Aidan Kehoe
Ar an naoú lá is fiche de mí Méan Fómhair, scríobh Uwe Brauer:
> Either I use defalias or comment out that line when I load a file and try
> to do something I get an alarming message of the sort
>
> (stack-overflow "Variable binding depth exceeds
> max-specpdl-size")
>
> To be precise
>
> Debugger entered--Lisp error: (stack-overflow "Variable binding depth exceeds max-specpdl-size")
> sort(((5.010001 "September Gnus v0.1" nil gnus-convert-old-ticks) (5.090008 "Oort Gnus v0.08" "legacy-gnus-agent" gnus-agent-convert-to-compressed-agentview) (5.1007 "Gnus v5.10.7" "legacy-gnus-agent" gnus-agent-unlist-expire-days) (5.1007 "Gnus v5.10.7" "legacy-gnus-agent" gnus-agent-unhook-expire-days)) car-less-than-car)
>
That is *possibly* the bug fixed by this:
http://mid.gmane.org/19636.40130.86152.626691＠parhasard.net
Though your backtrace is not actually a circular-list error.
It might be better to just add the definition of float-time to your
~/.xemacs/init.el, and use an unmodified 21.5.29.
--
‘Iodine deficiency was endemic in parts of the UK until, through what has been
described as “an unplanned and accidental public health triumph”, iodine was
added to cattle feed to improve milk production in the 1930s.’
(EN Pearce, Lancet, June 2011)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Re: subr.el (21.5.31) for 21.5.29
13 years, 2 months
Aidan Kehoe
Aidan Kehoe
Ar an naoú lá is fiche de mí Méan Fómhair, scríobh Uwe Brauer:
> I am confused:
>
> Do you really mean
> ;;(define-function 'special-form-p 'special-operator-p)
I did, but I had forgotten that the implementation of subr-arity uses it
further down.
> But then the compilation gives the same result.
Really? I would have imagined that it would throw a warning, not an error.
> shouldn't it be
> (defalias 'special-operator-p 'special-form-p)
That would work too, and is probably almost ideal for your circumstances.
(Ideal, of course, would be to have the support for X-Symbol that you need
included.)
--
‘Iodine deficiency was endemic in parts of the UK until, through what has been
described as “an unplanned and accidental public health triumph”, iodine was
added to cattle feed to improve milk production in the 1930s.’
(EN Pearce, Lancet, June 2011)
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
subr.el (21.5.31) for 21.5.29
13 years, 2 months
Uwe Brauer
Uwe Brauer
Hello
I tried to byte compile subr.el from 21.5.31 and I obtain
the function special-operator-p is not known to be defined.
Is this a new build in function?
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 3 participants
- 2 comments
float-time (was: cannot use no gnus 0.18: Xemacs 21.5.29)
13 years, 2 months
Uwe Brauer
Uwe Brauer
>> Regarding Re: cannot use no gnus 0.18: Xemacs 21.5.29;
>> Lars Magne Ingebrigtsen <larsi(a)gnus.org> adds:
> Uwe Brauer <oub(a)mat.ucm.es> writes:
>> I downloaded the latest gnus version via git (no gnus 0.18)
>> compiled it (using Xemacs 21.5.29 Mule) but when I tried to
>> use it I obtain an error which I attach (that is why I use
>> old 0.11 since in 0.18 I cannot use gnus-bug.
>> Debugger entered--Lisp error: (void-function float-time)
>> float-time((20099 10862 963059))
> Seems odd:
> `float-time' is a compiled Lisp function
> -- loaded from "/home/larsi/src/xemacs/lisp/subr.elc"
> (float-time &optional SPECIFIED-TIME)
Hello
It seems that the subr.el file shipped in 25.5.31 is
different from the one shipped in either 21.4.22 or 21.5.29.
I cannot upgrade to Xemacs 21.5.31 (due to the xsymbol patch
which is not applied to 21.5.31 since it was so far rejected
as being too "aggressive") so can I (and for that matter
other users) simply upgrade the subr.el file or is there
some incompatibility.
BTW not upgrading will prevent to use a recent version of
gnus!
regards
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 1 participants
- 0 comments
Re: vc-checkin: with headers always begin of buffer (rcs)
13 years, 2 months
Uwe Brauer
Uwe Brauer
>> Regarding Re: vc-checkin: with headers always begin of buffer (rcs); Julian Bradfield <jcb+xeb(a)jcbradfield.org> adds:
>> Any idea why good old save-excursion does not work in your code?
> I don't have a save-excursion.
> If your question is, why don't I have save-excursion, the answer is
> probably that I didn't understand save-excursion when I wrote that
> quick hack decades ago.
> I don't know whether it would work.
> I think it wouldn't; because probably checkin/out deletes all the
> existing text from the buffer (thereby pushing both point and mark to
> the beginning) before inserting the new text.
Well but this behavior only happens if there are keywords in the
buffer so I am not sure about your explanation.
I have the feeling there is a (goto-char (point-min)) call
in the code, if there are keywords in the buffer. However I
have failed to find such a line.
Uwe
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 3 participants
- 2 comments