From: Eli Zaretskii <eliz@gnu.org>
To: Amin Bandali <bandali@gnu.org>
Cc: eric@ericabrahamsen.net, 44506@debbugs.gnu.org
Subject: bug#44506: 28.0.50; Segfault on opening a particular message in Gnus in terminal/tty
Date: Mon, 09 Nov 2020 09:04:58 +0200 [thread overview]
Message-ID: <33F3730E-AF53-4CCC-B688-DEC41075CC69@gnu.org> (raw)
In-Reply-To: <87imafp2b4.fsf@gnu.org>
On November 9, 2020 6:43:59 AM GMT+02:00, Amin Bandali <bandali@gnu.org> wrote:
> Eli Zaretskii writes:
>
> [...]
> >
> > Thanks. One more thing, and then I need to think how this could
> > happen:
> >
> > (gdb) frame 3
>
> #3 0x00005555555a000c in update_frame_line (f=0x555556113798,
> vpos=24, updating_menu_p=false) at dispnew.c:5089
>
> >
> > (gdb) print (desired_row->glyphs[1])[149]
> >
>
> $1 = {
> charpos = -1,
> object = XIL(0),
> pixel_width = 0,
> ascent = 0,
> descent = 0,
> voffset = 0,
> type = 0,
> multibyte_p = false,
> left_box_line_p = false,
> right_box_line_p = false,
> overlaps_vertically_p = false,
> padding_p = false,
> glyph_not_available_p = false,
> avoid_cursor_p = false,
> resolved_level = 0,
> bidi_type = 0,
> face_id = 0,
> font_type = 0,
> slice = {
> img = {
> x = 0,
> y = 0,
> width = 0,
> height = 0
> },
> cmp = {
> from = 0,
> to = 0
> },
> glyphless = {
> upper_xoff = 0,
> upper_yoff = 0,
> lower_xoff = 0,
> lower_yoff = 0
> }
> },
> u = {
> ch = 32,
> cmp = {
> automatic = false,
> id = 16
> },
> img_id = 32,
> stretch = {
> height = 32,
> ascent = 0
> },
> glyphless = {
> method = 0,
> for_no_font = false,
> len = 4,
> ch = 0
> },
> val = 32
> }
> }
>
>
> Thanks.
Thanks, but this seems to be from a different GDB session? The vpos is 24 instead of 29 and the data of the glyph structure clearly differs from what pgrowx displayed in your previous report? I need consistent and coherent data from the same crash.
Or maybe you can come up with a reproduction recipe ? That'd really make the debugging much more efficient...
next prev parent reply other threads:[~2020-11-09 7:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 18:39 bug#44506: 28.0.50; Segfault on opening a particular message in Gnus in terminal/tty Amin Bandali
2020-11-07 18:58 ` Eli Zaretskii
2020-11-07 20:03 ` Amin Bandali
2020-11-07 20:29 ` Eli Zaretskii
2020-11-08 4:03 ` Eric Abrahamsen
2020-11-08 14:56 ` Eli Zaretskii
2020-11-08 18:27 ` Amin Bandali
2020-11-08 18:54 ` Eli Zaretskii
2020-11-08 19:20 ` Eli Zaretskii
2020-11-08 20:39 ` Amin Bandali
2020-11-09 3:31 ` Eli Zaretskii
2020-11-09 4:43 ` Amin Bandali
2020-11-09 7:04 ` Eli Zaretskii [this message]
2020-11-09 15:57 ` Eli Zaretskii
2020-11-10 5:42 ` Amin Bandali
2020-11-10 5:48 ` Eric Abrahamsen
2020-11-10 15:31 ` Eli Zaretskii
2020-11-13 5:20 ` Amin Bandali
2020-11-14 12:14 ` Eli Zaretskii
2020-11-14 17:19 ` Amin Bandali
2022-04-22 13:38 ` Lars Ingebrigtsen
2020-11-08 4:05 ` Eric Abrahamsen
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=33F3730E-AF53-4CCC-B688-DEC41075CC69@gnu.org \
--to=eliz@gnu.org \
--cc=44506@debbugs.gnu.org \
--cc=bandali@gnu.org \
--cc=eric@ericabrahamsen.net \
/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).