This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug threads/10227] GDB resumes inferior unexpectedly when receivingignored signal; step/next behave as continue


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]