From: Eli Zaretskii <eliz@gnu.org>
To: Sam Steingold <sds@gnu.org>
Cc: 28176@debbugs.gnu.org
Subject: bug#28176: 26.0.50; Emacs hangs on entering a specific article in gnus
Date: Wed, 23 Aug 2017 05:27:03 +0300 [thread overview]
Message-ID: <83fucj9fyg.fsf@gnu.org> (raw)
In-Reply-To: <CAFsbZ7YmChDxBVC8Y60Gf6thmfwfvaWKj=oFE8rc7siG-4Qzyw@mail.gmail.com> (message from Sam Steingold on Tue, 22 Aug 2017 15:18:11 -0400)
> From: Sam Steingold <sds@gnu.org>
> Date: Tue, 22 Aug 2017 15:18:11 -0400
> Cc: 28176@debbugs.gnu.org
>
> the backtrace _may_ depend on where I happen to hit C-c.
Yes, I understand.
> I am prepared to play "remote debugging" if you want to, supplying the output to the lldb (not gdb!) commands
> that you will send me.
> game?
Sorry, I don't know lldb well enough to play. But if you succeed to
hit a breakpoint in Fsignal and we then succeed to understand which
code signals an error and what error, we may be on our way to solve
the problem.
Or are you saying you don't know how to set a breakpoint in a
function?
Thanks.
next prev parent reply other threads:[~2017-08-23 2:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 16:09 bug#28176: 26.0.50; Emacs hangs on entering a specific article in gnus Sam Steingold
2017-08-21 16:24 ` Eli Zaretskii
2017-08-21 17:23 ` Sam Steingold
2017-08-21 17:41 ` Eli Zaretskii
2017-08-21 18:46 ` Sam Steingold
2017-08-21 19:03 ` Eli Zaretskii
2017-08-21 19:40 ` Sam Steingold
2017-08-22 15:09 ` Eli Zaretskii
2017-08-22 18:23 ` Sam Steingold
2017-08-22 19:10 ` Eli Zaretskii
2017-08-22 19:18 ` Sam Steingold
2017-08-23 2:27 ` Eli Zaretskii [this message]
2017-08-23 17:03 ` Sam Steingold
2017-08-23 18:21 ` Eli Zaretskii
2017-08-23 12:11 ` Charles A. Roelli
2017-08-23 13:34 ` Sam Steingold
2017-08-23 14:29 ` Charles A. Roelli
2017-08-23 19:10 ` Alan Third
2017-08-23 19:56 ` Charles A. Roelli
2017-08-23 20:16 ` Alan Third
2017-08-21 19:10 ` Eli Zaretskii
2017-08-21 19:44 ` Sam Steingold
2017-08-22 15:07 ` Eli Zaretskii
2017-08-22 22:21 ` npostavs
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=83fucj9fyg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28176@debbugs.gnu.org \
--cc=sds@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 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.