From: Eli Zaretskii <eliz@gnu.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: 16126@debbugs.gnu.org, dmantipov@yandex.ru
Subject: bug#16126: 24.3.50; segfault on Cygwin
Date: Fri, 13 Dec 2013 09:58:09 +0200 [thread overview]
Message-ID: <83txed5gj2.fsf@gnu.org> (raw)
In-Reply-To: <b4ma9g5i49j.fsf@jpl.org>
> Date: Fri, 13 Dec 2013 16:44:40 +0900
> From: Katsumi Yamaoka <yamaoka@jpl.org>
> Cc: 16126@debbugs.gnu.org
>
> Dmitry Antipov wrote:
> > On 12/13/2013 06:07 AM, Katsumi Yamaoka wrote:
> >> Program received signal SIGSEGV, Segmentation fault.
> >> 0x0053c90d in font_close_object (font_object=font_object@entry=538803829)
> >> at font.c:2902
> >> 2902 FRAME_DISPLAY_INFO (font->frame)->n_fonts--;
>
> > Do you have --enable-checking enabled?
>
> Ok, I used --enable-checking=yes and CFLAGS=-O0, and rebuilt
> Emacs.
>
> > If font->frame is not NULL, could you also please do:
> > (gdb) p *font->frame
> > and
> > (gdb) p *font->frame->output_data.x->display_info
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x005ce4d5 in font_close_object ()
> (gdb) p font->frame
> No symbol "font" in current context.
> (gdb) p *font->frame
> No symbol "font" in current context.
> (gdb) p *font->frame->output_data.x->display_info
> No symbol "font" in current context.
>
> Hm, there is no meaningful info, isn't it?
> Before this I rebuilt Emacs without specifying CFLAGS, and got
> ``value has been optimized out'' for all those.
There was a discussion yesterday on the Cygwin list about a similar
problem (I think), and the solution was to do some cleanup with your
font configuration. Perhaps your problem is similar?
next prev parent reply other threads:[~2013-12-13 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 2:07 bug#16126: 24.3.50; segfault on Cygwin Katsumi Yamaoka
2013-12-13 6:47 ` Dmitry Antipov
2013-12-13 7:44 ` Katsumi Yamaoka
2013-12-13 7:58 ` Eli Zaretskii [this message]
2013-12-13 8:36 ` Katsumi Yamaoka
2013-12-13 8:48 ` Eli Zaretskii
2013-12-13 9:57 ` Katsumi Yamaoka
2013-12-16 4:02 ` Katsumi Yamaoka
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=83txed5gj2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16126@debbugs.gnu.org \
--cc=dmantipov@yandex.ru \
--cc=yamaoka@jpl.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 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.