bug#34051: 27.0.50; Emacs 27 from master segfaults

[Stefan Husmann]

Eli Zaretskii <eliz@gnu.org> writes:

> [Please use Reply All to keep the bug address on the list of addressees.]
>
>
> Thanks, but this not useful because Emacs vforked and GDB stayed with
> the wrong process.  Maybe it will be easier for you to convert the
> backtrace of addresses you posted with the original report to a
> human-readable backtrace; the procedure to do that is described in the
> Emacs manual in the node "Crashing".

Hello, I had to recompile emacs without symbols stripped and here is the
output:

emacs_backtrace
??:?
terminate_due_to_signal
??:?
emacs_abort
??:?
message3_nolog
??:?
message3
??:?
Fmessage
??:?
Ffuncall
??:?
exec_byte_code
??:?
Ffuncall
??:?
exec_byte_code
??:?
Ffuncall
??:?
exec_byte_code
??:?
funcall_lambda
eval.c:?
Ffuncall
??:?
funcall_nil
eval.c:?
run_hook_with_args
??:?
run_hook
??:?
Fkill_emacs
??:?
x_connection_closed
xterm.c:?
x_error_quitter.isra.52
xterm.c:?
x_error_handler
xterm.c:?
??
??:0
??
??:0
??
??:0
??
??:0
??
??:0
x_parse_color
??:?
x_defined_color
??:?
load_color2
xfaces.c:?
realize_face
xfaces.c:?
lookup_face.isra.22
xfaces.c:?
face_at_string_position
??:?
handle_face_prop
xdisp.c:?
handle_stop
xdisp.c:?
next_element_from_string
xdisp.c:?
get_next_display_element
xdisp.c:?
display_string
xdisp.c:?
display_mode_element
xdisp.c:?
display_mode_element
xdisp.c:?
display_mode_element
xdisp.c:?
display_mode_element
xdisp.c:?

Best Regards

Stefan Husmann