From: "Yotam Medini יותם מדיני" <yotam.medini@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 11850@debbugs.gnu.org, Chong Yidong <cyd@gnu.org>
Subject: bug#11850: crash (null font) running emacs built from git
Date: Sun, 8 Jul 2012 18:58:30 +0300 [thread overview]
Message-ID: <CAAE-6rZn4S+1tJSoUB1L5S_c6c7B7FSJ-Zi6kz=HHKq35pTJOw@mail.gmail.com> (raw)
In-Reply-To: <837guj4ffq.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
I applied this patch, build with the config-switches you have suggested.
Running it (not thru gdb this time...) gave:
yotamm@huby:emacs:549> /usr/local/bin/emacs
xdisp.c:22676: Emacs fatal error: assertion failed: s->font
Fatal error (6)Aborted
I understand that Chong suggested some test steps.
Please resolve exactly what you would like me to try.
I would love to help, but my time with this environment
(where home-built emacs fails) is limited.
regards -- yotam
On Wed, Jul 4, 2012 at 8:14 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Wed, 4 Jul 2012 20:02:55 +0300
> > From: Yotam Medini יותם מדיני <yotam.medini@gmail.com>
> >
> > Could you please re-send your patch as an attachment.
> > So I can apply it cleanly (from the original) -
> > and not worry about white-space differences.
>
> You shouldn't need to worry, because I use Emacs to send the mail. ;-)
> So the whitespace is exactly as it is in the original patch. Besides,
> GNU 'patch' command accepts the --ignore-whitespace switch, even if
> something does happen to whitespace.
>
> But here's the patch as attachment, anyway:
>
>
[-- Attachment #2: Type: text/html, Size: 1756 bytes --]
next prev parent reply other threads:[~2012-07-08 15:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 11:27 bug#11850: crash (null font) running emacs built from git Yotam Medini יותם מדיני
2012-07-03 16:35 ` Eli Zaretskii
2012-07-03 16:49 ` Eli Zaretskii
2012-07-04 14:31 ` Yotam Medini יותם מדיני
2012-07-04 16:32 ` Eli Zaretskii
2012-07-04 20:49 ` bug#11850: bug#11813: " Eli Zaretskii
2012-07-05 7:34 ` Left Right
2012-07-05 13:17 ` bug#11850: " Eli Zaretskii
2012-07-05 13:33 ` Left Right
2012-07-05 16:54 ` Eli Zaretskii
2012-07-07 22:42 ` Left Right
2012-07-07 22:58 ` bug#11850: " Left Right
2012-07-08 3:00 ` Eli Zaretskii
2012-07-08 14:20 ` Chong Yidong
2012-07-08 15:56 ` bug#11850: " Eli Zaretskii
2012-07-08 16:29 ` Left Right
2012-07-08 18:40 ` bug#11850: " Jan Djärv
2012-07-09 4:21 ` Chong Yidong
2012-07-11 17:36 ` Left Right
2012-07-12 7:18 ` Chong Yidong
2012-08-16 3:25 ` Chong Yidong
2012-08-16 10:51 ` bug#11813: " Left Right
2012-08-26 4:36 ` Chong Yidong
2012-09-19 13:01 ` Left Right
[not found] ` <CAAE-6rb+efByT+um7KB-MfvmN2QbOiq_GRRmuwN7drsDu8TC_A@mail.gmail.com>
[not found] ` <837guj4ffq.fsf@gnu.org>
2012-07-08 15:58 ` Yotam Medini יותם מדיני [this message]
2012-07-08 16:43 ` Eli Zaretskii
2012-07-03 17:15 ` Eli Zaretskii
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='CAAE-6rZn4S+1tJSoUB1L5S_c6c7B7FSJ-Zi6kz=HHKq35pTJOw@mail.gmail.com' \
--to=yotam.medini@gmail.com \
--cc=11850@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=eliz@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).