Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>, gdb@sourceware.org
Subject: Re: Inadvertently run inferior threads
Date: Sat, 14 Mar 2015 13:40:00 -0000	[thread overview]
Message-ID: <55043A63.6020103@redhat.com> (raw)
In-Reply-To: <83h9tq3zu3.fsf@gnu.org>

On 03/12/2015 05:11 PM, Eli Zaretskii wrote:

> "pp" is in this case the command that invokes an inferior function,
> see src/.gdbinit in the Emacs sources for the details.

Here's a handy direct url:

  http://git.savannah.gnu.org/cgit/emacs.git/tree/src/.gdbinit

> Once this happens, the debugging session seems to be ruined: the only
> thing I can do is kill the inferior and quit the debugger.  Because
> there doesn't seem to be any way of stopping the threads again, not on
> Windows anyway.

The threads are probably stopped, and GDB managed to get out of
sync somehow.  Otherwise, "(gdb) interrupt" would probably work.

> Am I the only one who sees this annoying problem?  Does anyone know
> how to avoid it, or where to look for fixing it?

Never seen that, but then again I don't use Windows nowadays.

For run control bugs, logs are usually necessary to make sense of
things.  Try "set debug infrun 1" + the multiple Windows
specific "set debugfoo" commands.

Thanks,
Pedro Alves


  reply	other threads:[~2015-03-14 13:40 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12 17:11 Eli Zaretskii
2015-03-14 13:40 ` Pedro Alves [this message]
2015-03-14 14:56   ` Eli Zaretskii
2015-03-14 15:36     ` Pedro Alves
2015-03-14 15:51       ` Pedro Alves
2015-03-14 15:58         ` Pedro Alves
2015-06-10 15:15           ` Eli Zaretskii
2015-03-14 16:06         ` Eli Zaretskii
2015-06-10 15:50         ` Eli Zaretskii
2015-06-11 13:42           ` Eli Zaretskii
2015-06-15 13:18             ` Pedro Alves
2015-06-15 15:27               ` Eli Zaretskii
2015-06-15 15:42                 ` Pedro Alves
2015-06-23  4:07                   ` Doug Evans
2015-06-23 12:19                     ` Pedro Alves
2015-06-23 19:11                       ` Pedro Alves
2015-06-23 19:52                         ` Eli Zaretskii
2015-06-24 14:29                           ` Eli Zaretskii
2015-06-29 15:57                             ` Pedro Alves
2015-06-23 14:58                     ` Eli Zaretskii
2015-06-15 13:01           ` Pedro Alves
2015-06-15 15:14             ` Eli Zaretskii
2015-06-15 15:28               ` Pedro Alves
2015-06-15 17:21                 ` Eli Zaretskii
2015-06-15 17:56                   ` Pedro Alves
2015-06-15 19:07                     ` Eli Zaretskii
2015-06-23 11:51                     ` Pedro Alves
2015-03-14 16:04       ` Eli Zaretskii
2015-03-14 16:15         ` Pedro Alves
2015-03-14 16:17           ` Eli Zaretskii
2015-03-14 16:23             ` Pedro Alves
2015-03-14 17:01               ` Eli Zaretskii
2015-03-14 17:46                 ` Pedro Alves
2015-06-10 15:13     ` Eli Zaretskii
2015-06-15 13:08       ` Pedro Alves
2015-06-15 15:15         ` Eli Zaretskii

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=55043A63.6020103@redhat.com \
    --to=palves@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox