Re: Problem report.
14 years, 9 months
Aidan Kehoe
It helps a little, Gilberto; now we know that your binary has no debugging
symbols, so the backtrace would be of minimal use to us :-( . If you have
free time or a desire how to learn how these things work, you could try
compiling XEmacs, and repeating the attempt. “bt” is the short version of
the GDB command “backtrace”; you need to type it within GDB, not at the
shell prompt.
Ar an seachtú lá déag de mí Iúil, scríobh Gilberto:
> Does this it help? I can find a program call "bt", I am running on a Ubuntu
> machine and I am just a little bit more than a basic linux user. It looks to
> be something related to the graphics not being properly defined through the
> session.
>
> gdb /usr/bin/xemacs core
> GNU gdb 6.8-debian
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu"...
> (no debugging symbols found)
> /home/gilberto/cctv/tools/sw/ltib-imx27ads-20071219/rpm/BUILD/misc/test/mxc_
> vpu_test/core: No such file or directory.
> (gdb) run
> Starting program: /usr/bin/xemacs
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> [Thread debugging using libthread_db enabled]
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> [New Thread 0x7f7ea99606e0 (LWP 28952)]
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> ---Type <return> to continue, or q <return> to quit---
> (no debugging symbols found)
> Warning: Color name "Black" is not defined
> Warning: Color name "Gray80" is not defined
> Warning: Cannot convert string
> "-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*" to type FontStruct
> Warning: Missing charsets in String to FontSet conversion
> Warning: Cannot convert string
> "-*-helvetica-bold-r-*-*-*-120-*-*-*-*-iso8859-*,
> -*-*-*-*-*-*-*-120-*-iso10646-1,
> -*-*-*-*-*-*-*-120-*-jisx0208.1983-0,
> -*-*-*-*-*-*-*-120-*-jisx0201.1976-0" to type FontSet
> Warning: Missing charsets in String to FontSet conversion
> Warning: Color name "Gray30" is not defined
> Warning: Color name "Blue" is not defined
> Warning: Color name "Red" is not defined
> Warning: Color name "Maroon" is not defined
> Warning: Color name "ForestGreen" is not defined
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7f7ea99606e0 (LWP 28952)]
> 0x0000000000563b50 in ?? ()
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: Aidan Kehoe [mailto:kehoea＠parhasard.net]
> Sent: viernes, 17 de julio de 2009 11:57
> To: Gilberto
> Cc: xemacs-beta(a)xemacs.org
> Subject: Re: Problem report.
>
>
> Ar an séú lá déag de mí Iúil, scríobh Gilberto:
>
> > Starting Xemacs through a NXclient sesion reports this problem:
> >
> > Lisp backtrace follows:
> >
> > # bind (frame-being-created)
> > make-frame(nil #<x-device on "localhost:11.0" 0xb1e>)
> > frame-initialize()
> > # bind (debugger debug-on-error command-line-args-left)
> > command-line()
> > # (condition-case ... . ((t (byte-code " \ufffd\ufffd" ... 1))))
> > # bind (error-data)
> > normal-top-level()
> > # (condition-case ... . error)
> > # (catch top-level ...)
> >
> > [1] Segmentation fault xemacs vpu_codec.c
>
> Thanks, Gilberto! We can’t really do anything with that without a C
> backtrace (though I suppose we could research what NXclient is and try to
> reproduce it); could you attempt the same thing within GDB, and send us the
> C backtrace (type bt once the program has crashed) ?
>
> --
> ¿Dónde estará ahora mi sobrino Yoghurtu Nghe, que tuvo que huir
> precipitadamente de la aldea por culpa de la escasez de rinocerontes?
--
¿Dónde estará ahora mi sobrino Yoghurtu Nghe, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Problem report.
14 years, 9 months
Gilberto
Starting Xemacs through a NXclient sesion reports this problem:
Lisp backtrace follows:
# bind (frame-being-created)
make-frame(nil #<x-device on "localhost:11.0" 0xb1e>)
frame-initialize()
# bind (debugger debug-on-error command-line-args-left)
command-line()
# (condition-case ... . ((t (byte-code " \ufffd\ufffd" ... 1))))
# bind (error-data)
normal-top-level()
# (condition-case ... . error)
# (catch top-level ...)
[1] Segmentation fault xemacs vpu_codec.c
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Just to forestall any speculation ...
14 years, 9 months
SL Baur
Many of you know that I have worked at Cisco for the last couple of
years. Yes, I was in the blood bath that occurred today. Nearly everyone
on the floor of the building I work(ed) in got fired, including me.
This pretty much rules out any chance that I will be able to donate my
earlier work to Cisco (a bug tracking system front end written in emacs
lisp) to us. Sigh.
My position has been eliminated, so I have nothing left to lose by asking
one more time, but the prospects look hopeless. :(
-sb
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Face inheritance changed on Windows
14 years, 9 months
Ron Isaacson
Another weird one... between 21.5.28 and 21.5.29, it seems that the
effect of set-parent-face changed, only on Windows.
See the attached image. The definition of modeline-mousable is still
the same, but for some reason it's using the 'fallback' background
(the global default) instead of the one inherited from modeline.
This doesn't happen on X.
I'm not even sure where to start looking for this one... any pointers?
--
Ron Isaacson
Morgan Stanley
ron.isaacson(a)morganstanley.com / (212) 762-1051
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: Path changes in 21.5.29
14 years, 9 months
Stephen J. Turnbull
Ron Isaacson writes:
> All grumbling aside, I'm still struggling with this... I don't think
> the Makefile was properly updated to reflect the change from lib to
> share. The install-arch-dep target does:
Which Makefile? We have at least six that I can think of....
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
XEmacs Packages have been pre-released (2009-06-28-15)
14 years, 9 months
Norbert Koch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey there everyone.
... sorry for the delay ... vacation, new machine, outdated gpg key ...
I have just added the following packages to the 'Pre-Releases'
directory:
New Packages in Pre-Release:
===========================
eshell-1.18-pkg.tar.gz upstream version: 0fc80a3f6bb3bb59f42e9ff83cc8b89bf90fe658
Previously Announced Packages Still in Pre-Release:
==================================================
easypg-1.03-pkg.tar.gz upstream version: 0.0.16
general-docs-1.06-pkg.tar.gz upstream version: none
prog-modes-2.20-pkg.tar.gz upstream version: none
vc-1.46-pkg.tar.gz upstream version: none
Detailed Changes:
================
- ------- ChangeLog Entries from xemacs-packages/eshell/ChangeLog -------
2009-06-28 Norbert Koch <viteno(a)xemacs.org>
* Makefile (VERSION): XEmacs package 1.18 released.
2009-06-12 It's me FKtPp ;) <m_pupil(a)yahoo.com.cn>
* em-cmpl.el (eshell-cmpl-man-function): Use #'manual-entry
instead of #'man
* em-unix.el (eshell/man): Use #'manual-entry instead of #'man
Installing These:
================
Manually:
- --------
1) Download the packages that you want to install from:
/ftp.xemacs.org:/pub/xemacs/beta/experimental/packages/
2) Unpack them to: [1]
/usr/local/lib/xemacs/xemacs-packages/
3) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.[245].x):
- ----------------------------------------------
1) Tools -> Packages -> Add Download Site -> Pre-Releases
2) Tools -> Packages -> List and Install
3) Select the packages you wish to install (there are brief
instructions at the bottom of the packages buffer).
4) Packages -> Install/Remove Selected
5) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.1.14):
- -------------------------------------------
1) Options -> Manage Packages -> Add Download Site -> Pre-Releases
2) Options -> Manage Packages -> List and Install
3 - 5) As per XEmacs 21.[245].x.
norbert - XEmacs Package Release Manager.
Footnotes:
[1] Note: Mule packages should be installed into:
/usr/local/lib/xemacs/mule-packages/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFKSo22gu3ywdHdhM0RArqDAKDvfek+7vuYeTxewq53D3PmsraengCfW4HT
R2VSHbHQOF9LudUArBTyn2M=
=61rY
-----END PGP SIGNATURE-----
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
ruby-modes package updates
14 years, 9 months
Hans de Graaff
Hi,
In the process of cleaning up some stuff on my machine I came across an
update that I created for the ruby-modes packages. The current version
in CVS, 1.02, is quite out-of-date and my own version is synced to a
fairly recent upstream version (I think the one distributed with ruby
1.8.7).
I don't mind becoming maintainer for this package in XEmacs CVS if that
is what is needed to take this forward, although the result may be me
asking a bunch of elisp questions on the list :-)
Kind regards,
Hans
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
text-mode-syntax-table in 21.5
14 years, 9 months
Mike Kupfer
Karl Kleinpaste recently reported a problem with Gnus on the ding list,
where emphasis (e.g., making *foo* bold) wasn't happening if the text
appeared at the end of a line[1]. This was tracked down to a difference
in text-mode-syntax-table[2]:
The problem is due to the difference of the character syntax of
the newline character between XEmacs 21.5 and the others.
This form
(char-syntax ?\n text-mode-syntax-table)
returns `?\.' in XEmacs 21.5 whereas `? ' in XEmacs 21.4 and
FSFmacs.
Does anyone here know what the scoop is?
The problem was reported on 21.5.28, and I can reproduce it on
21.5.29.
mike
Footnotes:
[1] http://mid.gmane.org/vxkfxd4tmqd.fsf＠awol.kleinpaste.org
[2] http://mid.gmane.org/b4mab38u7ca.fsf＠jpl.org
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Patch for 21.5.29/objects-msw.c
14 years, 9 months
Ron Isaacson
Has anyone actually built 21.5.29 on Windows? MSVC (at least v7.1,
which I've been using for our builds) seems to follow the C89 rule
which requires all variable declarations to be at the top of the
block. As a result, the build fails with this error:
C:\tmp\xemacs\src\objects-msw.c(2082) : error C2275: 'HFONT' : illegal use of this type as an expression
because the declaration of 'hfont' is now preceded by non-declaration
code. Looks like this was introduced here:
http://thread.gmane.org/gmane.emacs.xemacs.beta/28907/focus=29165
The attached patch fixes it. I'm surprised nobody else has seen this,
unless there's some MSVC setting I'm missing...
--
Ron Isaacson
Morgan Stanley
ron.isaacson(a)morganstanley.com / (212) 762-1051
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta