all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Richard Kim <Richard.Kim1@synopsys.com>
Cc: 20331@debbugs.gnu.org
Subject: bug#20331: 24.5.50; stack trace of a segfault when using eww
Date: Fri, 25 Dec 2015 07:07:06 +0100	[thread overview]
Message-ID: <8737urf4dx.fsf@gnus.org> (raw)
In-Reply-To: <qtmr3rmhhgn.fsf@hydrox22.internal.synopsys.com> (Richard Kim's message of "Tue, 14 Apr 2015 08:12:24 -0700")

Richard Kim <Richard.Kim1@synopsys.com> writes:

> You should be able to save this email as an org file for more pleasant
> viewing.  The table of contents of this email is
>
>   Summary of the problem
>   Stack Trace
>     bt full
>   Info inserted by M-x report-emacs-bug
>
> * Summary of the problem
>
>   Emacs segfaults very often; just using eww (and even w3m) for few
>   minutes usually does it for me. So I compiled latest emacs from
>   emacs-24 branch with CFLAGS=-ggdb3 among others.  I then started first
>   emacs, then launched second emacs under gdb of the first.  I was able
>   to get a stack trace of the segfault when I was using eww.
>
> * Stack Trace
>
>    The stack trace seems to have resulted due to derefencing a null
>    pointer in line image.c:7469 shown here
>
>    : img->corners[TOP_CORNER] = gif->SavedImages[0].ImageDesc.Top;
>
>    where =gif=>SavedImages= is 0 as shown below:

Do you have an example image that makes Emacs segfault?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2015-12-25  6:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 15:12 bug#20331: 24.5.50; stack trace of a segfault when using eww Richard Kim
2015-12-25  6:07 ` Lars Ingebrigtsen [this message]
2016-02-02  4:34   ` Lars Ingebrigtsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8737urf4dx.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=20331@debbugs.gnu.org \
    --cc=Richard.Kim1@synopsys.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.