unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: 34394@debbugs.gnu.org, schwab@linux-m68k.org
Subject: bug#34394: 27.0.50; Emacs segfaults with SLY, company and C-g
Date: Sat, 09 Feb 2019 17:51:48 +0200	[thread overview]
Message-ID: <83wom9m02z.fsf@gnu.org> (raw)
In-Reply-To: <CALDnm51Dtg=W=e62511i329pS7J=2VYiAiDU8WRxTsY7OCGhBw@mail.gmail.com> (message from João Távora on Sat, 9 Feb 2019 15:37:23 +0000)

> From: João Távora <joaotavora@gmail.com>
> Date: Sat, 9 Feb 2019 15:37:23 +0000
> Cc: 34394@debbugs.gnu.org, Andreas Schwab <schwab@linux-m68k.org>
> 
> > Is it possible that somehow sit_for is called recursively in this
> > scenario?  If you put a breakpoint in sit_for, does it break when bt
> > shows another instance of sit_for up the call-stack?
> >
> > We need to establish who clobbers the jump_buf being used to implement
> > quitting by C-g.
> 
> The problem is that if I place a breakpoint there I can't work with company
> at all.  So I can't reproduce the problem.

Try a breakpoint that automatically continues the program, after it
displays the backtrace.  Like this:

  (gdb) break sit_for
  ....
  (gdb) commands
   > bt
   > continue
   > end






  reply	other threads:[~2019-02-09 15:51 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-09  0:55 bug#34394: 27.0.50; Emacs segfaults with SLY, company and C-g João Távora
2019-02-09  7:59 ` Eli Zaretskii
2019-02-09  9:45   ` João Távora
2019-02-09 10:10     ` Eli Zaretskii
2019-02-09 11:31       ` João Távora
2019-02-09 12:11         ` Eli Zaretskii
2019-02-09 12:33           ` Eli Zaretskii
2019-02-09 12:56             ` João Távora
2019-02-09 13:11               ` Eli Zaretskii
2019-02-09 13:23                 ` João Távora
2019-02-09 13:46                   ` Eli Zaretskii
2019-02-09 14:00                     ` João Távora
2019-02-09 14:01                       ` João Távora
2019-02-09 14:13                         ` João Távora
2019-02-09 14:36                           ` Eli Zaretskii
2019-02-09 15:21                           ` Eli Zaretskii
2019-02-09 15:37                             ` João Távora
2019-02-09 15:51                               ` Eli Zaretskii [this message]
2019-02-09 16:04                                 ` João Távora
2019-02-09 16:14                                   ` João Távora
2019-02-09 16:20                                     ` Eli Zaretskii
2019-02-09 16:26                                       ` João Távora
2019-02-09 20:08                                         ` João Távora
2019-02-10 16:42                                           ` Eli Zaretskii
2019-02-12 17:25                                             ` Eli Zaretskii
2019-02-12 18:10                                               ` João Távora
2019-02-12 18:29                                                 ` Eli Zaretskii
2019-02-12 19:15                                                   ` Eli Zaretskii
2019-02-12 20:42                                                     ` João Távora
2019-02-13 16:26                                                       ` Eli Zaretskii
2019-02-18 20:42                                                         ` João Távora
2019-02-19  3:28                                                           ` Eli Zaretskii
2019-02-09 16:21                                   ` Eli Zaretskii
2019-02-09 14:48                       ` Eli Zaretskii
2019-02-09 11:38       ` João Távora
2019-02-09  8:08 ` Andreas Schwab

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=83wom9m02z.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34394@debbugs.gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=schwab@linux-m68k.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 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).