[SAC21.5R21.4] Add 21.5 MULE regexp tests
22 years
Stephen J. Turnbull
Stephen J. Turnbull
SUPERSEDES APPROVE COMMIT 21.5 RECOMMEND 21.4
Please FUT xemacs-beta (Reply-To set).
>>>>> "DU" == Daiki Ueno <daiki(a)xemacs.org> writes:
tests/ChangeLog addition:
2002-12-24 Daiki Ueno <daiki(a)xemacs.org>
* automated/regexp-tests.el: Add a couple of cases which fail with
the current 21.5 MULE.
Thanks for refining the test case, and for the new test suite cases!
It looks to me like what is happening is that the character classes
are matching Mule characters on the basis of the low-order byte. Note
that with an odd high octet, bit 7 of the Mule Emchar is 1, and Emchar
ch1 truncated to the low octet != ?A. (I suspect that the trivial [A]
case does not assert against ch0 because it gets optimized to a pure
string match.) It seems to be specific to classes, not the regexp
engine in general, because forcing a regexp match instead of a string
match with the "＠?A" format doesn't assert.
Unfortunately I won't have time to work on this for a while, so feel
free to fix. :-) Ben gets back in mid-January, he probably won't be
able to work on it until late January at the earliest.
I've rewritten the patch pretty much completely, and suggest the
following hints for writing tests:
1. Include related successful cases. Fixes often break something.
2. Use the Known-Bug-Expect-Failure macro to mark the cases you know
are going to fail. We want to be able to distinguish between
regressions and other unexpected failures, and cases that have
been (partially) analyzed but not yet repaired.
3. Mark the bug with the date of report. I plan to add an "Unfixed
since yyyy-mm-dd" gloss to Known-Bug-Expect-Failure to further
increase developer embarrassment (== incentive to fix the bug),
but until then at least put a comment about the date so we can
easily see when it was reported.
4. It's a matter of judgement, but I used `eq' instead of `=' for the
successful match cases. My logic is that I don't want failures of
those assertions reported as "other failures" (a wrong-type-arg is
signaled, rather than a null return), I want them reported as
"assertion failures".
Here's my patch:
Index: tests/ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/tests/ChangeLog,v
retrieving revision 1.23
diff -u -U0 -r1.23 ChangeLog
--- tests/ChangeLog 11 Nov 2002 15:39:03 -0000 1.23
+++ tests/ChangeLog 27 Dec 2002 06:02:36 -0000
＠＠ -1 +1,8 ＠＠
-2002-10-19 Stephen Turnbull <steve＠tleepslib1>
+2002-12-27 Stephen J. Turnbull <stephen(a)xemacs.org>
+
+ * automated/regexp-tests.el (Mule character class): New test
+ cases. Based on draft patch by Daiki Ueno <daiki(a)xemacs.org>.
+
+ * automated/test-harness.el (Print-Pass): Comment.
+
+2002-10-19 Stephen J. Turnbull <stephen(a)xemacs.org>
Index: tests/automated/test-harness.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/tests/automated/test-harness.el,v
retrieving revision 1.7
diff -u -r1.7 test-harness.el
--- tests/automated/test-harness.el 11 Nov 2002 15:39:07 -0000 1.7
+++ tests/automated/test-harness.el 27 Dec 2002 06:02:04 -0000
＠＠ -158,6 +158,7 ＠＠
(defun Print-Pass (fmt &rest args)
(setq fmt (concat "PASS: " fmt))
+ ;; #### should warn if expecting failure here!
(and test-harness-verbose
(princ (concat (apply #'format fmt args) "\n"))))
Index: tests/automated/regexp-tests.el
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacs/tests/automated/regexp-tests.el,v
retrieving revision 1.4
diff -u -r1.4 regexp-tests.el
--- tests/automated/regexp-tests.el 11 Nov 2002 15:39:07 -0000 1.4
+++ tests/automated/regexp-tests.el 27 Dec 2002 06:02:04 -0000
＠＠ -221,7 +221,7 ＠＠
(insert "ab")
(goto-char (point-min))
(re-search-forward "\\(a\\)")
- ;; test the whole-match data, too -- one try scotched that, too!
+ ;; test the whole-match data, too -- one attempted fix scotched that, too!
(Assert (string= (match-string 0) "a"))
(Assert (string= (match-string 1) "a"))
(re-search-forward "b")
＠＠ -249,8 +249,33 ＠＠
(Assert (not (string-match "\\> " " ")))
(Assert (not (string-match "a\\<" "a")))
(Assert (not (string-match "\\>a" "a")))
+;; Added Known-Bug 2002-09-09
(Known-Bug-Expect-Failure
(Assert (not (string-match "\\b" "")))
(Assert (not (string-match "\\b" " ")))
(Assert (not (string-match " \\b" " ")))
(Assert (not (string-match "\\b " " "))))
+
+;; Character classes are broken in Mule as of 21.5.9
+;; Added Known-Bug 2002-12-27
+(if (featurep 'mule)
+ ;; note: (int-to-char 65) => ?A
+ (let ((ch0 (make-char 'japanese-jisx0208 52 65))
+ (ch1 (make-char 'japanese-jisx0208 51 65)))
+ (Assert (not (string-match "A" (string ch0))))
+ (Assert (not (string-match "[A]" (string ch0))))
+ (Known-Bug-Expect-Failure
+ (Assert (eq (string-match "[^A]" (string ch0)) 0)))
+ (Assert (not (string-match "＠A" (string ?＠ ch0))))
+ (Known-Bug-Expect-Failure
+ (Assert (not (string-match "＠[A]" (string ?＠ ch0)))))
+ (Known-Bug-Expect-Failure
+ (Assert (eq (string-match "＠[^A]" (string ?＠ ch0)) 0)))
+ (Assert (not (string-match "＠?A" (string ?＠ ch0))))
+ (Assert (not (string-match "A" (string ch1))))
+ (Assert (not (string-match "[A]" (string ch1))))
+ (Assert (eq (string-match "[^A]" (string ch1)) 0))
+ (Assert (not (string-match "＠A" (string ?＠ ch1))))
+ (Assert (not (string-match "＠[A]" (string ?＠ ch1))))
+ (Assert (eq (string-match "＠[^A]" (string ?＠ ch1)) 0))
+ (Assert (not (string-match "＠?A" (string ?＠ ch1))))))
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
- 1 participants
- 0 comments
Mario Konijnenburg is out of office
22 years
mario.konijnenburg＠philips.com
mario.konijnenburg＠philips.com
I will be out of the office starting 21-12-2002 and will not return until 06-01-2003.
- 1 participants
- 0 comments
RE: Re: union type is evil, redux
22 years
Ben Wing
Ben Wing
the crashes tend to occur in random places. they vary from one build to the next. often in pdump. vc++ does crash somewhere in pdump, in differing places from build to build. compiling sans union type makes the problem disappear.
once i tracked the problem down and it was that gcc did not do structure assignments completely in parallel in all situations. with sufficiently complicated expressions of the form x = f(x), where x is a structure, it would sometimes think that it had correctly computed one of the fields, and assign it a value, when in fact the old value was still needed elsewhere in the expression. i wrote to the gcc developers and they got very defensive and quoted a section of the ansi standard, saying "well, we agree your expected behavior is reasonable but *technically* it's not required by the ansi standard." this only happened with mule and error-checking, because the expression was much more complicated that way. by rewriting it using temporaries, the problem went away.
debugging problems with pdump is extremely difficult so i'd rather not do it when it's almost certainly a compiler problem.
why is everyone so keen on union type? the vc++ debugger is broken anyway when handling unions, as are many other debuggers. (it chokes and does not let you call debug_print() on a union.) furthermore, you can't type a raw union into a debugger expression, unlike an int. there is no guarantee that a compiler will correctly optimize a 4-byte union into a register. if you want the compiler to convert your 4-byte union into an int, just use an int for god's sake!
and if it does turn out we're relying on undefined behavior, then my question goes doubly, why do we want the union? there is *NO* undefined behavior with ints.
------- Original Message -------
On
Sat, 21 Dec 2002 17:08:30 +0300 Dmitry Bely?wrote:
"Ben Wing" <wing(a)666.com> writes:
> yes, i definitely have discovered compiler problems in the past. there's
> another message in which i wrote about this yesterday, i think.
Hmm, I have not found anything concrete.
> when
> expressions got too complicated, gcc failed to do structure assignments
> completely in parallel.
You told that VC++ also suffers from this "union bug". Can I see a piece
of code that reproduces it for VC++ 6.0 sp5? (or at least can you tell me
where it crashes in XEmacs)
> the bugs only occur usually when you turn on
> error-checking and mule, because these options greatly increase the
> complexity of the expressions. OCaml may simply not have any code with the
> expression complexity that we have.
Maybe. But I would rather believe into the code with undefined behaviour
(you know, C is a sort of mine field :-)), than in VC++ union bug (until I
see an example :-))
- Dmitry Bely
- 6 participants
- 16 comments
ispell on Windows
22 years
Samuel Harris Lipoff
Samuel Harris Lipoff
================================================================
Dear Bug Team!
Although the ispell package installs by the automated installer and
appears in the xemacs-packages\lisp subdirectory, it does not work!
When I try to launch the speller the minibuffer reports "No such file
or directory, ispell"
It is very important that the Windows version of xemacs works properly
with the standard packages, particularly the speller, as this is a
standard feature and necessary for many people's work.
I would be more than happy to provide any additional information that is
required, although I hope that you will find it all in the automatically
generated report below.
Yours,
--Samuel Lipoff
================================================================
System Info to help track down your bug:
---------------------------------------
OS version:
Microsoft Windows 2000 [Version 5.00.2195]
(Windows XP)
OS: Windows_NT
XEmacs 21.4.10 "Military Intelligence (Windows)" configured for
`i586-pc-win32'.
Building XEmacs in "f:\\xemacs\\xemacs-21.4-release\\nt".
Using compiler "cl -nologo -W3 -O2 -G5 -ML".
Installing XEmacs in "c:\\Program Files\\XEmacs\\XEmacs-21.4.10".
Package path is "~\\.xemacs;;c:\\Program
Files\\XEmacs\\site-packages;c:\\Program Files\\XEmacs\\xemacs-packages".
Compiling in support for Microsoft Windows native GUI.
Compiling in support for XPM images.
Compiling in support for GIF images.
Compiling in support for PNG images.
Compiling in support for TIFF images.
Compiling in support for JPEG images.
Compiling in support for X-Face message headers.
Compiling in support for toolbars.
Compiling in support for dialogs.
Compiling in support for widgets.
Compiling in support for native sounds.
Compiling in fast dired implementation.
Using portable dumper.
Load-Path Lisp Shadows:
----------------------
nil
Installed XEmacs Packages:
-------------------------
((zenirc:version 1.13 :type regular)
(xslt-process :version 1.11 :type regular)
(xslide :version 1.03 :type regular)
(xemacs-devel :version 1.48 :type single-file)
(xemacs-base :version 1.71 :type regular)
(w3 :version 1.26 :type regular)
(vm :version 7.07 :type regular)
(viper :version 1.35 :type regular)
(view-process :version 1.12 :type regular)
(vhdl :version 1.15 :type regular)
(vc-cc :version 1.21 :type regular)
(vc :version 1.33 :type regular)
(tramp :version 1.1 :type regular)
(tpu :version 1.12 :type regular)
(tooltalk :version 1.13 :type regular)
(tm :version 1.34 :type regular)
(time :version 1.12 :type regular)
(textools :version 1.13 :type regular)
(text-modes :version 1.55 :type single-file)
(texinfo :version 1.21 :type regular)
(supercite :version 1.19 :type regular)
(strokes :version 1.08 :type regular)
(speedbar :version 1.24 :type regular)
(sounds-wav :version 1.1 :type regular)
(sounds-au :version 1.1 :type regular)
(sml-mode :version 0.05 :type regular)
(slider :version 1.13 :type regular)
(sieve :version 1.1 :type regular)
(sh-script :version 1.16 :type regular)
(sgml :version 1.08 :type regular)
(semantic :version 1.14 :type regular)
(scheme :version 1.12 :type regular)
(sasl :version 1.12 :type regular)
(ruby-modes :version 1.0 :type single-file)
(rmail :version 1.13 :type regular)
(reftex :version 1.28 :type regular)
(python-modes :version 1.01 :type single-file)
(psgml-dtds :version 1.02 :type regular)
(psgml :version 1.35 :type regular)
(ps-print :version 1.08 :type regular)
(prog-modes
:version
1
.67
:type
single-file)
(pgg :version 1.01 :type regular)
(perl-modes :version 1.02 :type single-file)
(pcomplete :version 1.02 :type regular)
(pcl-cvs :version 1.64 :type regular)
(pc :version 1.25 :type single-file)
(os-utils :version 1.29 :type single-file)
(ocaml :version 0.03 :type regular)
(net-utils :version 1.28 :type single-file)
(mmm-mode :version 1.0 :type regular)
(misc-games :version 1.15 :type single-file)
(mine :version 1.14 :type regular)
(mh-e :version 1.16 :type regular)
(mew :version 1.17 :type regular)
(mailcrypt :version 2.12 :type regular)
(mail-lib :version 1.54 :type regular)
(liece :version 1.1 :type regular)
(jde :version 1.38 :type regular)
(ispell :version 1.24 :type regular)
(ilisp :version 1.28 :type regular)
(igrep :version 1.1 :type regular)
(idlwave :version 1.27 :type regular)
(ibuffer :version 1.08 :type regular)
(hm--html-menus :version 1.18 :type regular)
(haskell-mode :version 1.03 :type regular)
(gnus :version 1.64 :type regular)
(gnats :version 1.15 :type regular)
(games :version 1.13 :type regular)
(fsf-compat :version 1.11 :type single-file)
(frame-icon :version 1.09 :type regular)
(fortran-modes :version 1.01 :type single-file)
(forms :version 1.14 :type regular)
(footnote :version 1.15 :type regular)
(eudc :version 1.36 :type regular)
(eterm :version 1.13 :type regular)
(ess :version 1.02 :type regular)
(eshell :version 1.03 :type regular)
(emerge :version 1.09 :type regular)
(elib :version 1.1 :type single-file)
(eieio :version 1.03 :type regular)
(efs :version 1.29 :type regular)
(edt :version 1.12 :type regular)
(edit-utils :version 1.95 :type single-file)
(ediff :version 1.44 :type regular)
(edebug :version 1.14 :type regular)
(ecrypto :version 0.12 :type regular)
(docbookide :version 0.05 :type regular)
(dired :version 1.12 :type regular)
(dictionary :version 1.11 :type regular)
(debug :version 1.16 :type regular)
(crisp :version 1.12 :type regular)
(cookie :version 1.14 :type regular)
(clearcase :version 1.04 :type regular)
(cc-mode :version 1.31 :type regular)
(calendar :version 1.19 :type regular)
(calc :version 1.23 :type regular)
(c-support :version 1.16 :type single-file)
(build :version 1.07 :type regular)
(bbdb :version 1.21 :type regular)
(auctex :version 1.32 :type regular)
(apel :version 1.25 :type regular)
(ada :version 1.11 :type regular)
(Sun :version 1.13 :type regular))
Features:
--------
(mail-abbrevs xemacsbug shadow sendmail rfc822 zenirc-autoloads
xslt-process-autoloads xslide-autoloads xemacs-devel-autoloads
xemacs-base-autoloads w3-autoloads vm-autoloads viper-autoloads
view-process-autoloads vhdl-autoloads vc-cc-autoloads vc-autoloads
tramp-autoloads tpu-autoloads tooltalk-autoloads tm-autoloads
time-autoloads textools-autoloads text-modes-autoloads
texinfo-autoloads supercite-autoloads strokes-autoloads
speedbar-autoloads sounds-wav-autoloads sounds-au-autoloads
sml-mode-autoloads slider-autoloads sieve-autoloads
sh-script-autoloads sgml-autoloads semantic-autoloads scheme-autoloads
sasl-autoloads ruby-modes-autoloads rmail-autoloads reftex-autoloads
python-modes-autoloads psgml-dtds-autoloads psgml-autoloads
ps-print-autoloads prog-modes-autoloads pgg-autoloads
perl-modes-autoloads pcomplete-autoloads pcl-cvs-autoloads
pc-autoloads os-utils-autoloads ocaml-autoloads net-utils-autoloads
mmm-mode-autoloads misc-games-autoloads mine-autoloads mh-e-autoloads
mew-autoloads mailcrypt-autoloads mail-lib-autoloads liece-autoloads
jde-autoloads ispell-autoloads ilisp-autoloads igrep-autoloads
idlwave-autoloads ibuffer-autoloads hm--html-menus-autoloads
haskell-mode-autoloads gnus-autoloads gnats-autoloads games-autoloads
fsf-compat-autoloads frame-icon-autoloads fortran-modes-autoloads
forms-autoloads footnote-autoloads eudc-autoloads eterm-autoloads
ess-autoloads eshell-autoloads emerge-autoloads elib-autoloads
eieio-autoloads efs-autoloads edt-autoloads edit-utils-autoloads
ediff-autoloads edebug-autoloads ecrypto-autoloads
docbookide-autoloads dired-autoloads dictionary-autoloads
debug-autoloads crisp-autoloads cookie-autoloads clearcase-autoloads
cc-mode-autoloads calendar-autoloads calc-autoloads
c-support-autoloads build-autoloads bbdb-autoloads auctex-autoloads
apel-autoloads ada-autoloads Sun-autoloads lisp-autoloads loadhist
auto-show fontl-hooks code-cmds gutter-items menubar-items x-menubar
dragdrop mode-motion mouse itimer auto-save lisp-mode easymenu
iso8859-1 page buff-menu lib-complete help-nomule cus-file derived
frame text-props obsolete cus-start custom widget cl-extra mini-cl cl
cl-19 packages backquote very-early-lisp file-coding
mswindows-scrollbars mswindows toolbar native-sound scrollbar
network-streams subprocesses menu-accelerator-support menubar md5
xemacs gutter tiff png gif jpeg xface xpm xbm lisp-float-type
windows-nt dragdrop-api dialog devices window-system base64)
Recent keystrokes:
-----------------
misc-user
Recent messages (most recent first):
-----------------------------------
Loading xemacsbug...done
Loading xemacsbug...
- 3 participants
- 2 comments
Re: AW: [C] [packages (semantic)] Sync to upstream 1.4.1
22 years
Ville Skyttä
Ville Skyttä
[moved to -beta]
On Thu, 2002-12-26 at 17:38, Berndl, Klaus wrote:
> Maybe it would be a better idea waiting for next release 1.4.2 because
> 1.4.1 contains a buggy (too old) file semantic-util-modes.el which is
> responsible for some annoying behaviour of semantic 1.4.1.
I asked Eric about whether the sync (using the semantic-util-modes.el
from the 1.4, which is newer than what's in 1.4.1) would be a good idea
and he thought so.
The start of the ChangeLog entry also notes this:
> 2002-12-25 Ville Skyttä <scop(a)xemacs.org>
>
> * Sync to upstream version 1.4.1, plus typo fixes. Note that
> due to packaging buglet, semantic-util-modes.el is the one
> from 1.4 (an older version crept in the new upstream release).
--
\/ille Skyttä
scop at xemacs.org
- 1 participants
- 0 comments
calc broken?
22 years
Barry Warsaw
Barry Warsaw
Dear Bug Team!
I'm using calc 1.23 and I'm up-to-date w.r.t. all packages, with
XEmacs 21.4.10. With xemacs -vanilla, then M-x calc RET, I get the
following error:
Symbol's function definition is void: calc-record-compilation-date-macro
Loading calc...
Did the latest calc package break it?
-Barry
================================================================
System Info to help track down your bug:
---------------------------------------
uname -a: Linux geddy 2.4.18-17.7.x #1 Tue Oct 8 13:33:14 EDT 2002 i686 unknown
./configure '--with-mule'
XEmacs 21.4.10 "Military Intelligence" configured for `i686-pc-linux'.
Compilation / Installation:
Source code location: /usr/local/src/xemacs-21.4.10
Installation prefix: /usr/local
Operating system description file: `s/linux.h'
Machine description file: `m/intel386.h'
Compiler: gcc -g -O3 -Wall -Wno-switch -Winline -Wmissing-prototypes -Wsign-compare -Wshadow
Relocating allocator for buffers: no
GNU version of malloc: yes
- Using Doug Lea's new malloc from the GNU C Library.
Linking with `-z nocombreloc'.
- Consider configuring with --pdump.
Window System:
Compiling in support for the X window system:
- X Windows headers location: /usr/X11R6/include
- X Windows libraries location: /usr/X11R6/lib
- Handling WM_COMMAND properly.
Using Lucid menubars.
Using Lucid scrollbars.
TTY:
Compiling in support for ncurses.
Compiling in support for GPM (General Purpose Mouse).
Images:
Compiling in support for GIF images (builtin).
Compiling in support for XPM images.
Compiling in support for PNG images.
Compiling in support for JPEG images.
Compiling in support for TIFF images.
Sound:
Compiling in support for sound (native).
Databases:
Compiling in support for Berkeley database.
Compiling in support for LDAP.
Compiling in support for PostgreSQL.
- Using PostgreSQL header file: libpq-fe.h
- Using PostgreSQL V7 bindings.
Internationalization:
Compiling in support for Mule (multi-lingual Emacs).
Compiling in support for XIM (X11R5+ I18N input method).
- Using raw Xlib to provide XIM support.
Mail:
Compiling in support for "dot-locking" mail spool file locking method.
Other Features:
Inhibiting IPv6 canonicalization at startup.
Compiling in support for dynamic shared object modules.
- 3 participants
- 2 comments
Segmentation fault
22 years
Jérémy HERVE
Jérémy HERVE
[ I do not speak english very well, I am french - please excuse-me then
for mistakes }
Hello.
I just compiled XEmacs 21.1.14 like that:
# sh configure
# make
# make install
I use Slackware 8.1 (1 CD version, bought at Ikarios.com, and CD comes
from LinuxCentral), fully installed. When I run XEmacs in console mode,
It work, but when I run it under XFree86 4.2, I display me the following
text:
========== copy ==========
bash-2.05a# xemacs
Fatal error (11).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
If you have access to the PROBLEMS file that came with your
version of XEmacs, please check to see if your crash is described
there, as there may be a workaround available.
Otherwise, please report this bug by running the send-pr
script included with XEmacs, or selecting `Send Bug Report'
from the help menu.
As a last resort send ordinary email to `crashes(a)xemacs.org'.
*MAKE SURE* to include the information in the command
M-x describe-installation.
If at all possible, *please* try to obtain a C stack backtrace;
it will help us immensely in determining what went wrong.
To do this, locate the core file that was produced as a result
of this crash (it's usually called `core' and is located in the
directory in which you started the editor, or maybe in your home
directory), and type
gdb /usr/local/bin/xemacs core
then type `where' when the debugger prompt comes up.
(If you don't have GDB on your system, you might have DBX,
or XDB, or SDB. A similar procedure should work for all of
these. Ask your system administrator if you need more help.)
Lisp backtrace follows:
# bind (frame-being-created)
make-frame(nil #<x-device on ":0.0" 0x1a21>)
frame-initialize()
# bind (debugger debug-on-error command-line-args-left)
command-line()
# (unwind-protect ...)
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)
Segmentation fault
bash-2.05a#
========== copy end ==========
And I will add, to finish, somthing that can be usefull for you :
========== copy ==========
bash-2.05a# gdb /usr/local/bin/xemacs core
GNU gdb 5.2
Copyright 2002 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 "i386-slackware-linux"...
/root/core: No such file or directory.
(gdb) run
Starting program: /usr/local/bin/xemacs-21.1.14
Program received signal SIGSEGV, Segmentation fault.
0x40214128 in XtInitializeWidgetClass () from /usr/X11R6/lib/libXt.so.6
(gdb) where
#0 0x40214128 in XtInitializeWidgetClass () from /usr/X11R6/lib/libXt.so.6
#1 0x4021445b in XtInitializeWidgetClass () from /usr/X11R6/lib/libXt.so.6
#2 0x40214620 in XtInitializeWidgetClass () from /usr/X11R6/lib/libXt.so.6
#3 0x40214f14 in _XtCreatePopupShell () from /usr/X11R6/lib/libXt.so.6
#4 0x40214fa5 in XtCreatePopupShell () from /usr/X11R6/lib/libXt.so.6
#5 0x08143e80 in x_create_widgets (f=0x83aad00, lisp_window_id=136862484,
parent=136862484) at frame-x.c:1952
#6 0x0814446b in x_init_frame_1 (f=0x83aad00, props=136862484) at
frame-x.c:2183
#7 0x080e61a7 in Fmake_frame (props=136862484, device=137753360) at
frame.c:383
#8 0x080a367b in funcall_recording_as (recorded_as=136958732, nargs=2,
args=0xbfffeba4)
at eval.c:3197
#9 0x080a7923 in Ffuncall (nargs=3, args=0xbfffeba4) at eval.c:3238
#10 0x080853f9 in Fbyte_code (bytestr=136133200, vector=136133272,
maxdepth=11)
at bytecode.c:416
#11 0x080a433b in funcall_lambda (fun=136133360, nargs=0,
arg_vector=0xbfffeea8)
at eval.c:3607
#12 0x080a3771 in funcall_recording_as (recorded_as=137299396, nargs=0,
args=0xbfffeea4)
at eval.c:3214
#13 0x080a7923 in Ffuncall (nargs=1, args=0xbfffeea4) at eval.c:3238
#14 0x080853f9 in Fbyte_code (bytestr=136268704, vector=136268820,
maxdepth=9)
at bytecode.c:416
#15 0x080a433b in funcall_lambda (fun=136269040, nargs=0,
arg_vector=0xbffff2a8)
at eval.c:3607
#16 0x080a3771 in funcall_recording_as (recorded_as=137442452, nargs=0,
args=0xbffff2a4)
at eval.c:3214
#17 0x080a7923 in Ffuncall (nargs=1, args=0xbffff2a4) at eval.c:3238
#18 0x080853f9 in Fbyte_code (bytestr=136266576, vector=136266760,
maxdepth=13)
at bytecode.c:416
#19 0x080a433b in funcall_lambda (fun=136267280, nargs=0,
arg_vector=0xbffff384)
at eval.c:3607
#20 0x080a3eed in apply_lambda (fun=136267280, numargs=0,
unevalled_args=136862484)
at eval.c:3511
#21 0x080a316e in Feval (form=137257196) at eval.c:3085
#22 0x080a75d2 in condition_case_1 (handlers=136862596, bfun=0x80a284c
<Feval>,
barg=137257196, hfun=0x808b9d4 <cmd_error>, harg=136862484) at
eval.c:1653
#23 0x0808ba5f in top_level_1 (dummy=136862484) at cmdloop.c:206
#24 0x080a74a4 in internal_catch (tag=136936856, func=0x808ba30
<top_level_1>,
arg=136862484, threw=0x0) at eval.c:1328
#25 0x0808b36a in initial_command_loop (load_me=136862484) at cmdloop.c:285
#26 0x0809ebce in xemacs_21_1_14_i686_pc_linux () at emacs.c:1725
#27 0x080a0300 in main (argc=1, argv=0xbffff824, envp=0xbffff82c) at
emacs.c:2142
#28 0x403b317d in __libc_start_main (main=0x80a01e8 <main>, argc=1,
ubp_av=0xbffff824,
init=0x8077230 <_init>, fini=0x8168d54 <_fini>, rtld_fini=0x4000a534
<_dl_fini>,
stack_end=0xbffff81c) at ../sysdeps/generic/libc-start.c:129
(gdb)
========== copy end ==========
Just a question... I do not really know if that mail is the good way to
report the bug, but it appear to me as the only one that exists...
and... I am a really newbie under linux, and never really used XEmacs...
I would like to use it and... do you know what can I do to fix that
problem ?
Thank you very much !
++
Jérémy.
PS: I forget to say: CPU : AMD Duron 800 MHz, 256 MB of RAM, 20 GB HDD
- 3 participants
- 2 comments
WE PRODUCE ALL KINDS OF UMBRELLA
22 years
umbrella＠chinaxingan.com
umbrella＠chinaxingan.com
Entireweb
AllTheWeb
Google
TrueSearch
ÍøÂ玎Ôì³É¹Š-ÉÌÖÇÍøÉÏÓªÏúÌ׌þ<br>
×öÖйú×îºÃµÄÓªÏúÈíŒþ-¹ŠÄÜ°üÀš£ºÐÅÏ¢·¢²Œ¡¢ÐÅÏ¢ËÑË÷¡¢ÓÊŒþËÑË÷¡¢ÓÊŒþȺ·¢<br>
×¢£º±ŸÐÅϢ͚¹ýÉÌÖÇÍøÉÏÓªÏúÌ׌þ·¢ËÍ£¬·¢ËÍÄÚÈÝÓë˹ʢ¹«ËŸÎÞ¹Ø
- 1 participants
- 0 comments
Chip Resetter for Epson Cartridges
22 years
rkm＠kalvins.com
rkm＠kalvins.com
Universal Chip Resetter for Epson cartridges will reset the "smart chip" on ALL Epson cartridges multiple times. Reset cartridge chips to factory specs, showing full ink levels and providing the same number of cycles as when the chip was new.
This device works indefinitely and can be extended by simply replacing the 3 small batteries the same way you would replace a battery in a wrist watch.
The following cartridges are compatible with the Universal Epson Chip Resetter: T007, T008, T009, T015, T016, T017, T018, T026, T027, T028, T029, T036, T037, T038, T039, T0321, T0322, T0323, T0324, T0421, T0422, T0423, T0424, ETC.
Epson Stylus Printer model numbers: 780, 785EPX, 790, 810, 820, 830, 870, 870LE, 875DC, 875DCS, 890, 895, 1270, 1280, 1290, 2000P, C41, C42, C50, C60, C61, C62, C80, C82, 680, 777, 777I, ETC.
Buy now just for $14.95 at http://kalvins.com
- 1 participants
- 0 comments