unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pavel@Janik.cz (Pavel Janík)
Cc: elf@ee.ryerson.ca, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: emacs dumps core using gnus
Date: Sat, 16 Feb 2002 10:35:54 +0100	[thread overview]
Message-ID: <m38z9trcp1.fsf@Janik.cz> (raw)
In-Reply-To: <8011-Fri15Feb2002205048+0200-eliz@is.elta.co.il> ("Eli Zaretskii"'s message of "Fri, 15 Feb 2002 20:50:49 +0200")

   From: "Eli Zaretskii" <eliz@is.elta.co.il>
   Date: Fri, 15 Feb 2002 20:50:49 +0200

   > > Dave Love posted to g.e.bugs that the Emacs configure script issues a
   > > message warning the user to carefully check the version of the ungif
   > > library before linking it in when building Emacs. I think that post
   > > is realted to this issue.
   > 
   > AFAIU, Pavel is trying to change Emacs so that it doesn't crash, even
   > with the buggy libungif.  I think this is a better way, since a
   > message printed by the configure script can go unnoticed among all the
   > other messages it prints.

The status right now is: I have two GIF files which can be shown with
display from ImageMagick (other tools works too), but Emacs 21.1 (and RC
and HEAD too) will crash after

     emacs -q -f auto-image-file-mode picture.gif

Right now, I have two such files. Yesterday, I have digged through
bug-gnu-emacs mail archives on fencepost, but there is only one GIF file,
breaksemacs.gif, but it works perfectly with 21.1 and RC (but was reported
to break Emacs before). Eli promised to send me three similar files
tomorrow. If you have saved some weird GIF or you have GIF which can
SIGSEGV Emacs (and we told that it is bug in libungif version), please,
send it to me!
-- 
Pavel Janík

echo Mhbqnrnes Stbjr | tr "[a-y]" "[b-z]"
                  -- Someone, somewhere...

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


  reply	other threads:[~2002-02-16  9:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <x0pu3iex5q.fsf@www.ee.ryerson.ca>
     [not found] ` <Pine.SUN.3.91.1020206130807.3481A-100000@is>
     [not found]   ` <15457.20348.248746.712978@gargle.gargle.HOWL>
2002-02-08 13:55     ` emacs dumps core using gnus Richard Stallman
2002-02-10  1:29       ` luis fernandes
2002-02-10 11:28         ` Eli Zaretskii
2002-02-11 18:48           ` Richard Stallman
2002-02-11 19:57             ` Eli Zaretskii
2002-02-13 15:37               ` Richard Stallman
2002-02-14 11:10                 ` Eli Zaretskii
2002-02-15 10:37                   ` Richard Stallman
2002-02-15 15:58                     ` luis fernandes
2002-02-15 18:50                       ` Eli Zaretskii
2002-02-16  9:35                         ` Pavel Janík [this message]
2002-02-16 21:56                         ` Richard Stallman
2002-02-16 21:56                       ` Richard Stallman

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=m38z9trcp1.fsf@Janik.cz \
    --to=pavel@janik.cz \
    --cc=elf@ee.ryerson.ca \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    /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).