February 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: crypt (or tar) breakage? 26 years, 1 month

SL Baur

Adrian Aichner <aichner(a)ecf.teradyne.com> writes in xemacs-beta(a)xemacs.org: >>>>>> "SL" == SL Baur <steve(a)xemacs.org> writes: ... SL> With current CVS sources (almost b63) if I do: I mean 21.0.64. ... SL> Sigh. I'm going to have to track this down before making SL> 21.0.63 and 21.2.11. > Huh? I am running (emacs-version) "XEmacs 21.0 \"Pyrenean63\" [Lucid] > (i386-pc-win32) of Sat Feb 06 1999 on ZJ75T" already. Did you mean to > say 21.0.64? Yes, sorry. I'm not used to having the version number changed after I get all patches applied.

1 participants
0 comments

Re: crypt (or tar) breakage? 26 years, 1 month

Adrian Aichner

>>>>> "SL" == SL Baur <steve(a)xemacs.org> writes: SL> nbecker <nbecker(a)fred.net> writes in xemacs-beta(a)xemacs.org: >> No, but if I do xemacs -q, load-lib crypt, then visit the file it >> works. So you're correct that it is some interaction with some other >> package. I'll try to isolate it, but my .emacs is getting pretty >> large, so this may take some time... SL> O.K. I've just noticed a worse problem. SL> With current CVS sources (almost b63) if I do: SL> xemacs -vanilla SL> M-: (require 'crypt) SL> C-x C-f cvs-1.10.5.tar.gz SL> When I hit enter at the prompt I get a core dump: SL> Fatal error (11). SL> ... SL> Lisp backtrace follows: SL> # bind (inhibit-quit) SL> passwd-read-key-sequence("Encryption key for cvs-1.10.5.tar? [RET to SL> ignore]: SL> ") SL> ... SL> (gdb) where SL> #0 0x3ff800ec508 in kill () from /usr/shlib/libc.so SL> #1 0x1200c3980 in fatal_error_signal (sig=1076522752) at emacs.c:262 SL> #2 0x120119810 in mule_encode (encoding=0x1, src=0x11fff6a30 SL> "＠A\r\200\003", SL> dst=0x1200675f8, n=536832832) at file-coding.c:2439 SL> warning: Hit beginning of text section without finding SL> warning: enclosing function for address 0x11fff7058 SL> Sigh. I'm going to have to track this down before making SL> 21.0.63 and 21.2.11. Huh? I am running (emacs-version) "XEmacs 21.0 \"Pyrenean63\" [Lucid] (i386-pc-win32) of Sat Feb 06 1999 on ZJ75T" already. Did you mean to say 21.0.64? Adrian -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

1 participants
0 comments

Assertion failure in redisplay code whilst displaying MIME 26 years, 1 month

Philip Aston

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.0 "Pyrenean63" [Lucid] (i686-pc-cygwin32) of Thu Feb 18 1999 on ps02235 configured using `configure -with-png -with-xpm --site-includes=/usr/local/include' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: In VM, if I middle-click a MIME message or message digest object I get an assertion failure in the scrolling/redisplay caching code. Line 577 in indent.c: elt = point_in_line_start_cache (w, orig, (vtarget < 0 ? -vtarget : vtarget)); /* #### This assertion must be true before the if statements are hit but may possibly be wrong after the call to point_in_line_start_cache if orig is outside of the visible region of the buffer. Handle this. */ => assert (elt >= 0); I don't grok the redisplay code, so its not immediately obvious what's going on here. - Phil

1 participants
0 comments

Re: crypt (or tar) breakage? 26 years, 1 month

SL Baur

nbecker <nbecker(a)fred.net> writes in xemacs-beta(a)xemacs.org: > No, but if I do xemacs -q, load-lib crypt, then visit the file it > works. So you're correct that it is some interaction with some other > package. I'll try to isolate it, but my .emacs is getting pretty > large, so this may take some time... O.K. I've just noticed a worse problem. With current CVS sources (almost b63) if I do: xemacs -vanilla M-: (require 'crypt) C-x C-f cvs-1.10.5.tar.gz When I hit enter at the prompt I get a core dump: Fatal error (11). ... Lisp backtrace follows: # bind (inhibit-quit) passwd-read-key-sequence("Encryption key for cvs-1.10.5.tar? [RET to ignore]: ") ... (gdb) where #0 0x3ff800ec508 in kill () from /usr/shlib/libc.so #1 0x1200c3980 in fatal_error_signal (sig=1076522752) at emacs.c:262 #2 0x120119810 in mule_encode (encoding=0x1, src=0x11fff6a30 "＠A\r\200\003", dst=0x1200675f8, n=536832832) at file-coding.c:2439 warning: Hit beginning of text section without finding warning: enclosing function for address 0x11fff7058 Sigh. I'm going to have to track this down before making 21.0.63 and 21.2.11.

1 participants
0 comments

ediff question 26 years, 1 month

Steve Dickey

How do I use ediff from within PCL-CVS to examine changes when a file is marked as -patched- by cvs? Currently, I get an error that: ediff can only merge files marked.... I only have read access to the xemacs tree. Or am I doing something really stupid? -- Steve

3 participants
2 comments

Re: Copyright question for XEmacs icons. 26 years, 1 month

Ken Case

> Where does the OmniGroup come into this? Jonathan made these by > adapting from icons used by Omniweb. Two of those icons are Omni's (the third and the last), the rest appear to have been icons which ship with Mac OS X Server (Rhapsody), most of them used in the MailViewer and ProjectBuilder apps (and a few also used in OmniWeb). We probably wouldn't have a problem with you using our two icons (though I'd need to check to be certain), but you might have trouble getting permission from Apple to use the others. Ken

1 participants
0 comments

Solaris 2.5.1 + EGCS 1.1.1 + MULE: b63 failed 26 years, 1 month

Damon Lipparelli

The first time the executable is run ("testing for lisp shadows"), it crashes with the following stack trace. FWIW, building without MULE works. I've updated my "lisp" tree to get the new "mule" subdirectory, and have removed my old "mule-base" package. -lipp #0 0xef0748e8 in kill () #1 0x7a900 in fatal_error_signal (sig=11) at emacs.c:262 #2 <signal handler called> #3 0x4a734 in mark_object (obj=540550144) at alloc.c:3170 #4 0x5f53c in mark_char_table (obj=2, markobj=0x4a64c <mark_object>) at chartab.c:145 #5 0x4a77c in mark_object (obj=540801024) at alloc.c:3180 #6 0x4a8ac in mark_object (obj=4000924) at alloc.c:3234 #7 0x4a854 in mark_object (obj=2977792) at alloc.c:3216 #8 0x4c26c in garbage_collect_1 () at alloc.c:4493 #9 0x7e6c8 in Feval (form=1078462908) at eval.c:2919 #10 0x107e54 in readevalloop (readcharfun=541587968, sourcename=1615332676, evalfun=0x7e460 <Feval>, printflag=0) at lread.c:1341 #11 0x107000 in Fload_internal (file=1615332676, no_error=268435455, nomessage=268434432, nosuffix=2772992, codesys=-1607541148, used_codesys=-1607639036) at lread.c:747 #12 0x7f3c4 in funcall_recording_as (recorded_as=1, nargs=5, args=0xefffd4a8) at eval.c:3193 #13 0x83710 in Ffuncall (nargs=6, args=0xefffd4a8) at eval.c:3238 #14 0x56344 in Fbyte_code (bytestr=1613132116, vector=-2144964060, maxdepth=351232) at bytecode.c:416 #15 0x806b8 in funcall_lambda (fun=539390740, nargs=3, arg_vector=0xefffd75c) at eval.c:3597 #16 0x7f708 in funcall_recording_as (recorded_as=1, nargs=3, args=0xefffd758) at eval.c:3214 #17 0x83710 in Ffuncall (nargs=4, args=0xefffd758) at eval.c:3238 #18 0x56344 in Fbyte_code (bytestr=1612609064, vector=-2145487288, maxdepth=351232) at bytecode.c:416 #19 0x7ec50 in Feval (form=1075738136) at eval.c:3063 #20 0x7c278 in condition_case_1 (handlers=1075738208, bfun=0x7e460 <Feval>, barg=1075738136, hfun=0x7c2c4 <run_condition_case_handlers>, harg=-1607638940) at eval.c:1653 #21 0x8352c in condition_case_3 (bodyform=1075738136, var=-1607638940, handlers=1075738208) at eval.c:1715 #22 0x56870 in Fbyte_code (bytestr=1612608984, vector=-2145487368, maxdepth=351232) at bytecode.c:576 #23 0x806b8 in funcall_lambda (fun=538867556, nargs=1, arg_vector=0xefffdd3c) at eval.c:3597 #24 0x7f708 in funcall_recording_as (recorded_as=1, nargs=1, args=0xefffdd38) at eval.c:3214 #25 0x82e1c in call1 (fn=1, arg0=1614203412) at eval.c:3238 #26 0xdebc8 in mapcar1 (leni=48, vals=0x0, fn=538867556, seq=1078003580) at fns.c:3237 #27 0xe1318 in Fmapc (fn=538867556, seq=1078003580) at fns.c:3320 #28 0x7f4b4 in funcall_recording_as (recorded_as=1, nargs=2, args=0xefffe030) at eval.c:3197 #29 0x83710 in Ffuncall (nargs=3, args=0xefffe030) at eval.c:3238 #30 0x56344 in Fbyte_code (bytestr=1612609424, vector=-2145486936, maxdepth=351232) at bytecode.c:416 #31 0x806b8 in funcall_lambda (fun=538867640, nargs=2, arg_vector=0xefffe2dc) at eval.c:3597 #32 0x7f708 in funcall_recording_as (recorded_as=1, nargs=2, args=0xefffe2d8) at eval.c:3214 #33 0x83710 in Ffuncall (nargs=3, args=0xefffe2d8) at eval.c:3238 #34 0x56344 in Fbyte_code (bytestr=1612609552, vector=-2145486808, maxdepth=351232) at bytecode.c:416 #35 0x806b8 in funcall_lambda (fun=538867772, nargs=1, arg_vector=0xefffe804) at eval.c:3597 #36 0x7f708 in funcall_recording_as (recorded_as=1, nargs=1, args=0xefffe800) at eval.c:3214 #37 0x83710 in Ffuncall (nargs=2, args=0xefffe800) at eval.c:3238 #38 0x56344 in Fbyte_code (bytestr=1612904540, vector=-2145191588, maxdepth=351232) at bytecode.c:416 #39 0x806b8 in funcall_lambda (fun=539163452, nargs=0, arg_vector=0xefffe950) at eval.c:3597 #40 0x800a0 in apply_lambda (fun=539163452, numargs=0, unevalled_args=-1607639036) at eval.c:3501 #41 0x7edb4 in Feval (form=1077330156) at eval.c:3085 #42 0x7c278 in condition_case_1 (handlers=-1607638940, bfun=0x7e460 <Feval>, barg=1077330156, hfun=0x6091c <cmd_error>, harg=-1607639036) at eval.c:1653 #43 0x609ac in top_level_1 (dummy=2771968) at cmdloop.c:206 #44 0x83430 in internal_catch (tag=-1607561116, func=0x60970 <top_level_1>, arg=-1607639036, threw=0x0) at eval.c:1328 #45 0x5ff8c in initial_command_loop (load_me=395632) at cmdloop.c:285 #46 0x79200 in sort_args (argc=2760704, argv=0xefffef5c) at emacs.c:1705 #47 0x7aae8 in main (argc=2, argv=0xefffef5c, envp=0xefffef68) at emacs.c:2122 --- I'm reporting for duty as a modern person. I want to do the Latin Hustle now!

1 participants
0 comments

Re: crypt (or tar) breakage? 26 years, 1 month

Neal D. Becker

>>>>> "Martin" == Martin Buchholz <martin(a)xemacs.org> writes: >>>>> "SL" == SL Baur <steve(a)xemacs.org> writes: SL> nbecker <nbecker(a)fred.net> writes in xemacs-beta(a)xemacs.org: >>> One of the coolest features of xemacs seems to be broken as of >>> 21.2b10. SL> I cannot duplicate this problem on either 21.0 or 21.2. >>> I have (require 'crypt) >>> If I visit a .tar.gz, it should not only ungzip, but will put me in tar >>> mode. That doesn't work anymore. Instead I get >>> c½ÅOé =i has size -59888002 - corrupted. >>> parsing tar file...2% >>> parsing tar file...1% >>> parsing tar file... SL> Are you sure you don't have a corrupted .tar.gz file? Martin> I have seen this error before, but also am not sure how to reproduce Martin> it. I suspect it might be dependent on order of loading and autoloads Martin> and such. Martin> Does it go away if you Martin> (require 'tar-mode) Martin> (require 'crypt) No, but if I do xemacs -q, load-lib crypt, then visit the file it works. So you're correct that it is some interaction with some other package. I'll try to isolate it, but my .emacs is getting pretty large, so this may take some time...

1 participants
0 comments

[Richard Stallman <rms@gnu.org>] Re: [Kyle Jones <kyle_jones@wonderworks.com>] Re: Bug in file-regular-p 26 years, 1 month

Hrvoje Niksic

file-regular-p uses stat() again.

1 participants
0 comments

Re: ediff question 26 years, 1 month

Adrian Aichner

>>>>> "Steve" == Steve Dickey <steved(a)cory.eecs.berkeley.edu> writes: Steve> How do I use ediff from within PCL-CVS to examine changes Steve> when a file is marked as -patched- by cvs? Hello Steve! A file status of Patched or Updated indicates the file to be identical to a certain revision in the repository. Hence there's nothing to (e)diff. e runs `cvs-mode-ediff' tells me: Can only merge `Modified', `Merged' or `Conflict' files HTH, Adrian Steve> Currently, I get an error that: ediff can only merge files Steve> marked.... Steve> I only have read access to the xemacs tree. Steve> Or am I doing something really stupid? Steve> -- Steve> Steve -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

1 participants
0 comments

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta February 1999