emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Building the igc branch on MS-Windows


From: Gerd Möllmann
Subject: Re: Building the igc branch on MS-Windows
Date: Fri, 26 Apr 2024 19:03:14 +0200
User-agent: Gnus/5.13 (Gnus v5.13)

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Helmut Eller <eller.helmut@gmail.com>
>> Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
>> Date: Fri, 26 Apr 2024 17:01:15 +0200
>> 
>> 
>> I have a nice test case, that crashes both GUI and tty versions.  Can
>> you reproduce this?
>> 
>> ./src/emacs -nw -Q --eval
>>   '(progn (view-hello-file) (redisplay) (igc--collect) (forward-line))'
>
> I can.  It crashes in both GUI and TTY cases, but with two very
> different backtraces.  Here's the GUI case, it looks very similar to
> what I see when scrolling through xdisp.c:
>
>   Thread 1 received signal SIGSEGV, Segmentation fault.
>   XCAR (c=0xab5ca1b) at lisp.h:751
>   751       return lisp_h_XLP (o);
>   (gdb) bt
>   #0  XCAR (c=0xab5ca1b) at lisp.h:751
>   #1  assoc_no_quit (key=<optimized out>, alist=0xab5ca1b) at fns.c:2032
>   #2  0x00afc0ed in font_list_entities (f=0xaa1c478, spec=0xa843cb5)
>       at font.c:2795
>   #3  0x00afce53 in font_find_for_lface (f=<optimized out>, f@entry=0xaa1c478,
>       attrs=<optimized out>, attrs@entry=0x727a2b0, spec=<optimized out>,
>       spec@entry=0xa843c15, c=<optimized out>, c@entry=-1) at font.c:3316

...

>   #13 0x0099cba9 in display_mode_line (w=w@entry=0xaa1c628,
>       face_id=MODE_LINE_ACTIVE_FACE_ID, format=0x1a24e953) at
>       lisp.h:1179

I wonder if this could also be caused by the missing tracing of global
variables in xdisp.c that I mention in the other mail. I would propose
to fix that first.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]