From: Daniel Barrett <dbarrett@blazemonger.com>
Cc: Daniel Barrett <dbarrett@blazemonger.com>,
bug-gnu-emacs@gnu.org, kyle_jones@wonderworks.com
Subject: Re: Emacs 22.0.50.1 crash on make_uninit_multibyte_string
Date: Sat, 22 Apr 2006 09:46:44 -0400 [thread overview]
Message-ID: <17482.13252.227555.498198@spinky.blazemonger.com> (raw)
In-Reply-To: m3zmqdgsou.fsf@kfs-l.imdomain.dk
In case anybody is interested, the "random crash" problem between Emacs and
Kyle Jones's VM package completely disappeared when I upgraded from SUSE
Linux 9.1 to 10.0. It's now been a month without a single segfault. Same
versions of Emacs and VM as before.
--
Dan Barrett
dbarrett@blazemonger.com
On September 16, 2005, Kim F. Storm wrote:
>I took a quick look at VM, and found this:
>
>> ;;(provide 'vm-byteopts)
>>
>> ;; get the compiler loaded so we can undo some of the things that
>> ;; happen when it's loaded.
>> (load "bytecomp" t t nil)
>> ;; Emacs 19 byte compiler complains about too much stuff by default.
>> ;; Turn off most of the warnings here.
>> (setq byte-compile-warnings '(free-vars))
>> ;; need to use these variables for v18 support.
>> ;; stifle the compiler.
>> (put 'inhibit-local-variables 'byte-obsolete-variable nil)
>> ;; Turn off dynamic docstrings and lazy function loading. This
>> ;; is a new feature of FSF Emacs 19.29, and is incompatible
>> ;; with pre-19.29 versions of FSF Emacs and all version of Lucid
>> ;; Emacs / XEmacs. I like being able to share .elc files between
>> ;; different v19 Emacses.
>> (setq byte-compile-dynamic nil)
>> (setq byte-compile-dynamic-docstrings nil)
>> ;; avoid v20 features because users are going
>> ;; to try to share elc files no matter what we tell them.
>> (setq byte-compile-emacs19-compatibility t)
>>
>> (provide 'vm-byteopts)
>
>
>I wonder if some of these settings may trigger some unusual
>byte-code pattern which we don't normally see in emacs 22.x ???
>
>
>Daniel Barrett <dbarrett@blazemonger.com> writes:
>
>> On September 8, 2005, Kim F. Storm wrote:
>>>Daniel Barrett <dbarrett@blazemonger.com> writes:
>>>> On September 8, 2005, Kim F. Storm wrote:
>>>>>Can you provide an "xbacktrace" and "bt full" backtrace.
>>
>> (gdb) xbacktrace
>> "vm-left-justify-string"
>> "vm-reencode-mime-encoded-words-in-string"
>> "format"
>> "list"
>> "eval"
>> "vm-summary-sprintf"
>> "vm-su-summary"
>> "vm-stuff-attributes"
>> "vm-stuff-virtual-attributes"
>> "vm-set-xxxx-flag"
>> "vm-set-new-flag"
>> "vm-show-current-message"
>> "vm-scroll-forward"
>> "call-interactively"
>>
>> (gdb) bt full
>> #0 make_uninit_multibyte_string (nchars=85, nbytes=85) at alloc.c:1880
>> string = Variable "string" is not available.
>>
>>>Please use M-x report-emacs-bug to include proper information
>>>about your emacs version and environment, including additional
>>>information about the crash (as instructed).
>>
>> In GNU Emacs 22.0.50.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
>> of 2005-07-19 on spinky
>> X server distributor `The XFree86 Project, Inc', version 11.0.40399902
>> configured using `configure '--prefix' '/usr/local/emacs-dev''
>>
>> Important settings:
>> value of $LC_ALL: nil
>> value of $LC_COLLATE: C
>> value of $LC_CTYPE: nil
>> value of $LC_MESSAGES: nil
>> value of $LC_MONETARY: nil
>> value of $LC_NUMERIC: nil
>> value of $LC_TIME: nil
>> value of $LANG: en_US.UTF-8
>> locale-coding-system: utf-8
>> default-enable-multibyte-characters: nil
>>
>> Major mode: VM Summary
>>
>> Minor modes in effect:
>> mouse-wheel-mode: t
>> tooltip-mode: t
>> auto-compression-mode: t
>> global-font-lock-mode: t
>> blink-cursor-mode: t
>> unify-8859-on-encoding-mode: t
>> utf-translate-cjk-mode: t
>> line-number-mode: t
>> next-error-follow-minor-mode: Fol
>>
>> Recent input:
>> [irrelevant -- run much later than the bug occurrence]
>>
>> Recent messages:
>> Reordering messages... done
>> 48 messages, 0 new, 0 unread, 0 deleted
>> Generating summary... 40
>> Generating summary markers...
>> Generating summary... done
>> 48 messages, 0 new, 0 unread, 0 deleted
>> Checking for new mail for /home/dbarrett/.Mail/emacs...
>> 48 messages, 0 new, 0 unread, 0 deleted
>> Mark set
>> Loading emacsbug...done
>>
>>
>
>--
>Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2006-04-22 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.6130.1126053675.20277.bug-gnu-emacs@gnu.org>
2005-09-08 11:26 ` Emacs 22.0.50.1 crash on make_uninit_multibyte_string Kim F. Storm
[not found] ` <17184.13523.891333.897902@spinky.blazemonger.com>
[not found] ` <m3aciny9tb.fsf@kfs-l.imdomain.dk>
2005-09-16 1:08 ` Daniel Barrett
2005-09-16 11:25 ` Kim F. Storm
2005-09-16 12:56 ` Daniel Barrett
2005-09-16 15:47 ` Daniel Barrett
2006-04-22 13:46 ` Daniel Barrett [this message]
2005-09-07 0:35 Daniel Barrett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17482.13252.227555.498198@spinky.blazemonger.com \
--to=dbarrett@blazemonger.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=kyle_jones@wonderworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).