Re: [Bug: 21.4.22] xemacs segfaults on sendmail-pre-abbrev-expand-hook
13 years, 1 month
Stephen J. Turnbull
Andreas, please make sure to at least CC the list. I live in a disaster area,
although my daily life is relatively unaffected (in fact, I have more than usual
time for my hobbies, but have lost access to a lot resources I use for them)
and cannot promise quick response. CC'ing xemacs-beta and not trimming.
On Mon, Mar 14, 2011 at 11:47 PM, Andreas Goesele <Goesele(a)hfph.mwn.de> wrote:
> "Stephen J. Turnbull" <stephenjturnbull(a)gmail.com> writes:
>
>> What we need to diagnose a crash, usually, is a C backtrace. If you know
>> how to force XEmacs to crash, you can usually get the backtrace by starting
>> XEmacs in a debugger. On systems with gdb, something like
>>
>> $ gdb /usr/local/bin/xemacs
>> (gdb) run
>> <some message about XEmacs crashing>
>> (gdb) bt
>> <long text of backtrace>
>>
>> Then save the terminal output to a file, and attach it to your report.
>> The backtrace will usually run off the screen. If that makes it difficult
>> to capture all the output, you can run gdb as
>>
>> $ gdb /usr/local/bin/xemacs 2>&1 | tee crash.log
>
> Strangely, on the day I reported the problem, I had a sure recipe to
> crash xemacs, but that doesn't work anymore. But once more writing an
> email resulted in a crash. This time not expanding an address, but just
> writing the first word. It seems it was linked to the following set of
> events:
>
> Parsing /home/user/.mailrc... done
> Parsing /home/user/.mailrc...
> Rebuilding aliases due to new aliases.
Which MUA are you using?
> Here there is the backtrace of the segfault. Given that there are no
> debugging symbols, I don't know, whether that helps.
No, it doesn't help much. However, I can tell from the backtrace that
you crashed in Ffuncall (aka the lisp function funcall) which is very strange.
Since you're using a no-mule build of 21.4, I suspect it is related to
non-ASCII characters, but can't be sure.
I don't know offhand if there's any way to get the numeric addresses
of the arguments to the last Ffuncall. If there is, you should be able
to get at least some Lisp information.
First, see if you have a copy of .gdbinit. If not you can get one from
http://hg.debian.org/hg/xemacs/xemacs-21.4/file/70c8d51df66c/src/.gdbinit.
Then load it into gdb with "source .gdbinit". Then you can use "lbt" to get
a Lisp backtrace (which probably isn't very informative), "lbp <lisp expr>" to
print the value of a Lisp expression, and "pobj" to convert C addresses to
Lisp object information.
> GNU gdb (GDB) 7.0.1-debian
> Copyright (C) 2009 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 "i486-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /usr/bin/xemacs21-nomule...(no debugging symbols found)...done.
> (gdb) run
> Starting program: /usr/bin/xemacs21-nomule
> [Thread debugging using libthread_db enabled]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x080b6468 in Ffuncall ()
> (gdb) bt
> #0 0x080b6468 in Ffuncall ()
> #1 0x08096997 in ?? ()
> #2 0x08096e42 in funcall_compiled_function ()
> #3 0x080b6643 in Ffuncall ()
> #4 0x080b73e9 in run_hook_with_args_in_buffer ()
> #5 0x080b7598 in run_hook_with_args ()
> #6 0x080b76e6 in Frun_hooks ()
> #7 0x080b7719 in run_hook ()
> #8 0x08088b62 in Fexpand_abbrev ()
> #9 0x0809ceab in ?? ()
> #10 0x0809d0c1 in Fself_insert_command ()
> #11 0x080b67a6 in Ffuncall ()
> #12 0x08097960 in Fcall_interactively ()
> #13 0x080b8e5d in Fcommand_execute ()
> #14 0x080e3f0a in ?? ()
> #15 0x080e5a10 in Fdispatch_event ()
> #16 0x0809c2dc in Fcommand_loop_1 ()
> #17 0x080b9aaa in condition_case_1 ()
> #18 0x0809c54a in ?? ()
> #19 0x080b4551 in internal_catch ()
> #20 0x0809c840 in initial_command_loop ()
> #21 0x080b19ff in xemacs_21_4_22_i486_pc_linux ()
> #22 0x080b24dc in main ()
>
>
> --
> Omnis enim res, quae dando non deficit, dum habetur et non datur,
> nondum habetur, quomodo habenda est.
> Augustinus, De doctrina christiana
>
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Re: [COMMIT] Be better about searching for chars typed via XIM and x-compose.el, isearch
13 years, 1 month
Aidan Kehoe
Good evening!
Myself and Mats accidentally went off-list with this discussion. In summary
of what we said there:
-- Mats didn’t see any immediate benefit with my patch. He saw the problems
he described earlier in isearch in Gnus Summary buffers and in isearches in
dired, and a distinct set of problems in isearches in Gnus Article buffers.
-- I managed to reproduce his dired and Gnus summary problem when I switched
to a German layout (rather than my modified Irish layout), where ä and ö
have keys to themselves). This can be avoided with a nil value for
try-alternate-layout-for-commands, and I now think that only language
environments with non-Latin scripts should have a non-nil default for this
variable.
-- Mats still has the distinct set of problems in isearches in Gnus Article
buffers, which I have yet to reproduce. (Am renewing my news.individual.net
subscription to that end.)
Mats is curious about the need for try-alternate-layouts-for-commands, so
here’s an attempt to explain what it does; for people in Russia or Greece,
the keyboard by default doesn’t generate Roman-alphabet characters. So it’s
actually comparatively a lot of work to type control f or control b. Not
*so* much of an issue for GUI programs, but much more of an issue for
XEmacs. If try-alternate-layouts-for-commands is non-nil, and command lookup
is about to fail (that is, a message like “C-ь C-ф not defined” would
normally be shown), XEmacs pretends for a second that the keyboard has a US
layout, works out that C-ь C-ф would correspond to C-x C-f on that, and
calls #'find-file interactively. It comes into play in isearch because of
the rewriting of commands that #'isearch-pre-command-hook does in order to
add characters that would normally self-insert to the search string.
Best,
Aidan
Ar an dara lá déag de mí Márta, scríobh Aidan Kehoe:
> [...]
--
“Apart from the nine-banded armadillo, man is the only natural host of
Mycobacterium leprae, although it can be grown in the footpads of mice.”
-- Kumar & Clark, Clinical Medicine, summarising improbable leprosy research
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
XEmacs Packages have been pre-released (2011-03-14-16)
13 years, 1 month
Norbert Koch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey there everyone.
I have just added the following packages to the 'Pre-Releases'
directory:
New Packages in Pre-Release:
===========================
pgg-1.08-pkg.tar.gz upstream version: 0.1
Previously Announced Packages Still in Pre-Release:
==================================================
leim-1.32-pkg.tar.gz upstream version: none
text-modes-2.00-pkg.tar.gz upstream version: none
x-symbol-1.13-pkg.tar.gz upstream version: 4.5.1
xemacs-base-2.30-pkg.tar.gz upstream version: none
xemacs-devel-1.82-pkg.tar.gz upstream version: none
Detailed Changes:
================
- ------- ChangeLog Entries from xemacs-packages/pgg/ChangeLog -------
2011-03-14 Norbert Koch <viteno(a)xemacs.org>
* Makefile (VERSION): XEmacs package 1.08 released.
2011-03-12 Aidan Kehoe <kehoea(a)parhasard.net>
* pgg-parse.el (pgg-parse-crc24, pgg-parse-crc24-string):
Call #'define-ccl-program at compile time, if available, not at
runtime. Addresses Marcus Crestani's problem of
http://mid.gmane.org/vpdhcif81o9.fsf＠informatik.uni-tuebingen.de .
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.
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)
iD8DBQFNfjvXgu3ywdHdhM0RAgInAJ9/Ecw5A6Z18KRsABS/ZO9wLfExvwCeKLQG
EZe52Wn7C0cqf0VLkhoRHvk=
=0fU2
-----END PGP SIGNATURE-----
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Fwd: XEmacs returns the wrong values for display-color-cells
13 years, 1 month
Stephen J. Turnbull
oops, forgot xemacs-beta. Sorry for the dupe, Jeff!
---------- Forwarded message ----------
From: Stephen J. Turnbull <stephenjturnbull(a)gmail.com>
Date: Mon, Mar 14, 2011 at 10:33 PM
Subject: Re: XEmacs returns the wrong values for display-color-cells
To: Jeff Sparkes <jsparkes(a)gmail.com>
On Mon, Mar 14, 2011 at 10:19 PM, Jeff Sparkes <jsparkes(a)gmail.com> wrote:
>> Maybe fo some future holographic display? :-)
>> I'll redo the patch with max 24 bits.
Thanks!
> I'd have done a bug report on tracker, but it's down right now.
> Should I also implement this for ttys? In tty-init.el we define the 16 ansi
> colors, but are they available in every tty?
Yes, if you know how to do it. In particular, the terminfo capability
max_colors
(just "colors" in terminfo files and "Co" in termcap files) should give you the
right answer on a properly configured system.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Re: smtpmail, starttls and gmail
13 years, 1 month
Raymond Toy
>>>>> "Uwe" == Uwe Brauer <oub(a)mat.ucm.es> writes:
Uwe> Raymond Toy wrote:
>>>>>>> "Uwe" == Uwe Brauer<oub(a)mat.ucm.es> writes:
>>
>> >>> Regarding Re: smtpmail, starttls and gmail; Raymond Toy
>> >>> <toy.raymond(a)gmail.com> adds:
>> >> Maybe I can just ignore the failure from delete-process.
>>
Uwe> That looks all odd to me, which OS do you use?
>>
>> I'm using Mac OSX 10.6.
>>
Uwe> Hm I thought I tried it out on Mac (not sure with version,
Uwe> but I thought I installed starttls using port)......
I'm using macports too, but I can't find starttls. I also see, now in
the console window that the starttls program is crashing. I can't
tell if it's crashing after the delete-process or before.
My smtp trace is quite similar to yours (when using starttls), except
I don't get the "Process SMTP killed". It just says "closing
connection xxxx".
Ray
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
smtpmail, starttls and gmail
13 years, 1 month
Raymond Toy
After a long time, I decided I should get xemacs working with my gmail
account. After lots of googling and experimenting, I finally got
xemacs to access my gmail account via imap. This is working fine.
But I can't send mail using smtp.gmail.com. Well, it does eventually
send the mail, but I get an error which makes gnus think the mail was
not sent.
My settings from custom.el are
'(message-send-mail-function 'smtpmail-send-it)
'(smtpmail-auth-credentials '(("smtp.gmail.com" 587 "toy.raymond(a)gmail.com" nil)))
'(smtpmail-debug-info t)
'(smtpmail-debug-verb t)
'(smtpmail-default-smtp-server "smtp.gmail.com")
'(smtpmail-local-domain nil)
'(smtpmail-smtp-server "smtp.gmail.com")
'(smtpmail-smtp-service 587)
'(smtpmail-starttls-credentials '(("smtp.gmail.com" 587 nil nil))
I have gnutls-cli too.
The contents of *trace SMTP* is appended below where I'm sending
myself a junk message. The message does get sent, though.
Is this a bug in smtpmail/starttls, gnutls-cli, smtp.gmail.com, or
something else? Surely there must be other people accessing gmail.com
with xemacs!
Ray
*trace of SMTP session*, but I deleted the AUTH_LOGIN parts in case
that contains my password.
220 mx.google.com ESMTP u45sm3037401yhn.9
Process SMTP exited abnormally with code 1
EHLO gondor.local
250-mx.google.com at your service, [24.148.170.2]
250-SIZE 35651584
250-8BITMIME
250-STARTTLS
250 ENHANCEDSTATUSCODES
STARTTLS
220 2.0.0 Ready to start TLS
EHLO gondor.local
250-mx.google.com at your service, [24.148.170.2]
250-SIZE 35651584
250-8BITMIME
250-AUTH LOGIN PLAIN XOAUTH
250 ENHANCEDSTATUSCODES
AUTH LOGIN
[deleted]
235 2.7.0 Accepted
MAIL FROM:<toy.raymond＠gmail.com> SIZE=311
250 2.1.0 OK u45sm3037401yhn.9
RCPT TO:<toy.raymond＠gmail.com>
250 2.1.5 OK u45sm3037401yhn.9
DATA
354 Go ahead u45sm3037401yhn.9
To: toy.raymond(a)gmail.com
Subject: testing4
From: Raymond Toy <toy.raymond(a)gmail.com>
Date: Fri, 11 Mar 2011 11:23:17 -0500
Message-ID: <m14o79hbii.fsf(a)gondor.local>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.5-b29 (darwin)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
testing4
.
250 2.0.0 OK 1299860605 u45sm3037401yhn.9
QUIT
221 2.0.0 closing connection u45sm3037401yhn.9
*** Fatal error: A TLS packet with unexpected length was received.
*** Server has terminated the connection abnormally.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
XEmacs returns the wrong values for display-color-cells
13 years, 1 month
Jeff Sparkes
(display-color-cells) returns 256 on my 24 bit X display. It returns 0 on
ms-windows. (It also returns 256 on gtk devices).
What's happening is that it's returning the size of the default colormap,
not largest possible one.
I made it return a float to avoid overflow with a 32 bit depth display.
--
Jeff Sparkes
jsparkes(a)gmail.com
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ediff obscures menu
13 years, 1 month
Rodney Sparapani
Boy, what is with me and bugs lately? I'm seeing a similar behavior to
what is described at
http://calypso.tux.org/pipermail/xemacs-beta/2004-July/002126.html
The differences are that I have the default toolbar-visible-p=t and ...
(custom-set-variables
'(default-gutter-position (quote top))
'(default-toolbar-position (quote left)))
But, I do see something similar. Rather than the toolbar being
obscured (it's vertical on the left); I see nearly the entire menu
obscured: I can only see File and the rest are covered by the
tabs. If I select a tab that's not in ediff-mode, then the tabs
drop and I can see the entire menu. If I go back to ediff-mode,
then the tabs cover the menu once again. I'm running 21.4.22 with
ediff-version=2.81.2 Anybody see that before?
Rodney
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Re:[Issue 717] [Bug: 21.4.22] Crash while idle
13 years, 1 month
Rodney Sparapani
On 06/22/10 10:28 AM, Rodney Sparapani wrote:
> On 06/22/10 10:00 AM, Stephen J. Turnbull wrote:
>>
>> Thanks. Looks like configure found alloca.h, which means the platform
>> alloca is being used, I suppose.
>
> I also looked at config.h and that's my reading as well.
>
> Thanks,
>
> Rodney
This bug is biting me almost daily now. I googled it and I see some
similarities with a previous bug report...
http://calypso.tux.org/pipermail/xemacs-beta/2006-July/009590.html
Does that help at all? If not, then I guess I have to bite the bullet
and move to xemacs-beta. Nothing similar is happening there, correct?
Thanks.
Rodney
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
cannot properly customize font-latex-...-face
13 years, 1 month
Giacomo Boffi
with a recent 21.5 (beta29) "garbanzo" and the last auctex package
from auctex people
if i try to customize font-latex-...-faces--- in particular i tried to
customize font-latex-slide-title-face --- i can change ONLY the
foreground color of the face
any suggestion?
tia
g
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta