public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/10227] GDB resumes inferior unexpectedly when receiving ignored signal; step/next behave as continue
Date: Wed, 04 Jul 2012 17:02:00 -0000	[thread overview]
Message-ID: <bug-10227-4717-Shdjc66pUK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-10227-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=10227

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2012-07-04
                 CC|                            |palves at redhat dot com
   Target Milestone|6.8                         |7.5
     Ever Confirmed|0                           |1

--- Comment #2 from Pedro Alves <palves at redhat dot com> 2012-07-04 17:02:24 UTC ---
Hi Paul,

This recent patch should have fixed this:

2012-06-28  Jan Kratochvil  <jan.kratochvil@redhat.com>
            Pedro Alves  <palves@redhat.com>

        * gdbthread.h (ALL_THREADS): New macro.
        (thread_list): Declare.
        * infrun.c (handle_inferior_event) <spurious signal>: Don't keep
        going, but instead fall through to the stepping handling.
        * linux-nat.c (resume_lwp): New parameter 'signo'.  Resume with
        the passed in signal.  Adjust debug output.
        (resume_callback): Rename to ...
        (linux_nat_resume_callback): ... this.  Pass the thread's last
        stop signal, if in "pass" state.
        (linux_nat_resume): Adjust to rename.
        (stop_wait_callback): New assertion.  Don't respawn signals;
        instead let the LWP remain with SIGNALLED set.
        (linux_nat_wait_1): Remove flushing of pending SIGSTOPs.
        * remote.c (append_pending_thread_resumptions): New.
        (remote_vcont_resume): Call it.
        * target.h (target_resume): Extend comment.

I tried both your tests with current mainline, and didn't see anything wrong. 
I checkout a gdb from just before that patch, and tries your first test, and
indeed it broke.

Can you confirm?

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


       reply	other threads:[~2012-07-04 17:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-10227-4717@http.sourceware.org/bugzilla/>
2012-07-04 17:02 ` palves at redhat dot com [this message]
2012-10-24 15:54 ` palves at redhat dot com
2012-10-24 16:02 ` ppluzhnikov at google dot com
2009-06-02  6:15 [Bug threads/10227] New: " ppluzhnikov at google dot com
2009-06-02  6:36 ` [Bug threads/10227] " ppluzhnikov at google dot com

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=bug-10227-4717-Shdjc66pUK@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).