unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 25959@debbugs.gnu.org
Subject: bug#25959: No stop button in gdb toolbar
Date: Mon, 06 Mar 2017 05:38:02 +0200	[thread overview]
Message-ID: <83pohvhy79.fsf@gnu.org> (raw)
In-Reply-To: <amefyb8eb4.fsf@fencepost.gnu.org> (message from Glenn Morris on Sun, 05 Mar 2017 19:00:15 -0500)

> From: Glenn Morris <rgm@gnu.org>
> Cc: 25959@debbugs.gnu.org
> Date: Sun, 05 Mar 2017 19:00:15 -0500
> 
> > What version of GDB do you have?
> 
> I should have said:
> GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-94.el7

Hmm... that might be too old.  Is there any chance you could try with
a newer one?  Or maybe you already did?

> > Anyway, I guess reverting only the first hunk of 2e78e6a suffices?
> 
> Right.
> 
> Though I don't know if it is safe to revert any of 2e78e6a, given that
> it says these signals never reply, and comments in
> https://debbugs.gnu.org/13845#8
> talks about gdb replying in order.

My problem with the original report is that the recipe for reproducing
the bug is so complex I cannot wrap my head around what's going on
there.  One way forard could be to see if reverting the first hunk of
2e78e6a reintroduces the problem in that recipe.  Or maybe we should
just revert it and see if anyone hollers.





  reply	other threads:[~2017-03-06  3:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 21:28 bug#25959: No stop button in gdb toolbar Glenn Morris
2017-03-03 22:35 ` Glenn Morris
2017-03-04  8:54   ` Eli Zaretskii
2017-03-06  0:00     ` Glenn Morris
2017-03-06  3:38       ` Eli Zaretskii [this message]
2017-03-06 18:01         ` Glenn Morris
2017-03-06 18:53           ` Eli Zaretskii
2017-03-06 19:41             ` Glenn Morris

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=83pohvhy79.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=25959@debbugs.gnu.org \
    --cc=rgm@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 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).