From: Eli Zaretskii <eliz@gnu.org>
To: 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 17:57:13 +0200 [thread overview]
Message-ID: <83y2ja4j6u.fsf@gnu.org> (raw)
In-Reply-To: <33F3730E-AF53-4CCC-B688-DEC41075CC69@gnu.org> (message from Eli Zaretskii on Mon, 09 Nov 2020 09:04:58 +0200)
> Date: Mon, 09 Nov 2020 09:04:58 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: eric@ericabrahamsen.net, 44506@debbugs.gnu.org
>
> 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...
Alternatively, if you can give me an ssh login on that system, and set
up an account for me so that I could reproduce the problem, I could
debug it remotely on your system.
next prev parent reply other threads:[~2020-11-09 15:57 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
2020-11-09 15:57 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y2ja4j6u.fsf@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 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.