[Bug win32/10004] New: gdb cannot continue after SIGFPE or SIGSEGV happen on windows

[Bug win32/10004] New: gdb cannot continue after SIGFPE or SIGSEGV happen on windows

[webpirat at mail dot ru]

I'm using free pascal compiler on windows xp to compile example application.
This is a simple program which handles division by zero (EDivByZero) exception 
and writes to the console when this happen.
Run without debugger gives next output:
Exception is handled
1

When I run it with gdb I cannot continue usual execution after SIGFPE happen.

(gdb) run
Starting program: C:\programming\mytest\debugger_exceptions/test_exception.exe
[New thread 6100.0x13e4]

Program received signal SIGFPE, Arithmetic exception.
0x00401502 in EXCEPTION1 () at test_exception.lpr:15
15          a := a div (a - 1); // EDivByZero
(gdb) continue
Continuing.

Program received signal SIGFPE, Arithmetic exception.
0x00401502 in EXCEPTION1 () at test_exception.lpr:15
15          a := a div (a - 1); // EDivByZero
(gdb) continue
Continuing.

Program exited with code 030000000224.

Ok, tried "info signals" and found that gdb handles SIGFPE. I changed behavior:

(gdb) handle SIGFPE noprint
Signal        Stop      Print   Pass to program Description
SIGFPE        No        No      Yes             Arithmetic exception
(gdb) handle SIGFPE nostop
Signal        Stop      Print   Pass to program Description
SIGFPE        No        No      Yes             Arithmetic exception
(gdb) run
Starting program: C:\programming\mytest\debugger_exceptions/test_exception.exe
[New thread 5912.0xa3c]

Program exited with code 030000000224. 

In this mail thread (http://lists.freepascal.org/lists/fpc-devel/2009-
March/016625.html) I've got a suggestion to create a bug report here.

-- 
           Summary: gdb cannot continue after SIGFPE or SIGSEGV happen on
                    windows
           Product: gdb
           Version: 6.8
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: win32
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: webpirat at mail dot ru
                CC: gdb-prs at sourceware dot org


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug win32/10004] gdb cannot continue after SIGFPE or SIGSEGV happen on windows

[webpirat at mail dot ru]

------- Additional Comments From webpirat at mail dot ru  2009-03-25 14:22 -------
Created an attachment (id=3843)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=3843&action=view)
compiled executable


-- 


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug win32/10004] gdb cannot continue after SIGFPE or SIGSEGV happen on windows

[webpirat at mail dot ru]

------- Additional Comments From webpirat at mail dot ru  2009-03-25 14:23 -------
Created an attachment (id=3844)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=3844&action=view)
free pascal source file


-- 


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug win32/10004] gdb cannot continue after SIGFPE or SIGSEGV happen on windows

[jonas dot maebe at elis dot ugent dot be]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jonas dot maebe at elis dot
                   |                            |ugent dot be


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug win32/10004] gdb cannot continue after SIGFPE or SIGSEGV happen on windows

[vsnijders at vodafonevast dot nl]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vsnijders at vodafonevast
                   |                            |dot nl


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug win32/10004] gdb cannot continue after SIGFPE or SIGSEGV happen on windows

[muller at ics dot u-strasbg dot fr]

------- Additional Comments From muller at ics dot u-strasbg dot fr  2009-03-27 08:51 -------
This is a Microsoft bug:
please see
http://support.microsoft.com/kb/173652

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at sourceware dot|muller at sourceware dot org
                   |org                         |
             Status|UNCONFIRMED                 |ASSIGNED


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug win32/10004] gdb cannot continue after SIGFPE or SIGSEGV happen on windows

[tromey at redhat dot com]

------- Additional Comments From tromey at redhat dot com  2009-03-27 15:18 -------
Unsetting target milestone.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|6.8                         |---


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug win32/10004] gdb cannot continue after SIGFPE or SIGSEGV happen on windows

[pierre.muller@ics-cnrs.unistra.fr]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 7008 bytes --]

https://sourceware.org/bugzilla/show_bug.cgi?id=10004

--- Comment #6 from pierre.muller@ics-cnrs.unistra.fr ---
  Hi Andreas,

  would it be also possible to completely removed
comment #5?

  Thanks in advance,

Pierre Muller

> -----Message d'origine-----
> De : schwab at sourceware dot org [mailto:sourceware-
> bugzilla@sourceware.org]
> Envoyé : mercredi 28 mai 2014 21:42
> À : muller@sourceware.org
> Objet : [Bug win32/10004] gdb cannot continue after SIGFPE or SIGSEGV
> happen on windows
> 
> https://sourceware.org/bugzilla/show_bug.cgi?id=10004
> 
> Andreas Schwab <schwab at sourceware dot org> changed:
> 
>            What    |Removed                     |Added
> -----------------------------------------------------------------------
> -----
>                  CC|jackie.rosen at hushmail dot com   |
> 
> --
> You are receiving this mail because:
> You are the assignee for the bug.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-15807-listarch-gdb-prs=sources.redhat.com@sourceware.org Thu May 29 11:52:00 2014
Return-Path: <gdb-prs-return-15807-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 10135 invoked by alias); 29 May 2014 11:51:59 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 10109 invoked by uid 55); 29 May 2014 11:51:59 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/15713] i386_linux_resume calls QUIT -> lock-up
Date: Thu, 29 May 2014 11:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: tdep
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: palves at redhat dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-15713-4717-1FffQtL12k@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-15713-4717@http.sourceware.org/bugzilla/>
References: <bug-15713-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-q2/txt/msg00313.txt.bz2
Content-length: 4055

https://sourceware.org/bugzilla/show_bug.cgi?id\x15713

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, master has been updated
       via  8817a6f225766029787b5e2c1300a342b328909e (commit)
      from  251bde03baf93dbb44d3785e09e03179916143e3 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;hˆ17a6f225766029787b5e2c1300a342b328909e

commit 8817a6f225766029787b5e2c1300a342b328909e
Author: Pedro Alves <palves@redhat.com>
Date:   Thu May 29 12:50:48 2014 +0100

    PR gdb/15713 - errors from i386_linux_resume lead to lock-up

    linux_nat_resume is not considering that linux_ops->to_resume may throw:

      /* Mark LWP as not stopped to prevent it from being continued by
         linux_nat_resume_callback.  */
      lp->stopped = 0;

      if (resume_many)
        iterate_over_lwps (ptid, linux_nat_resume_callback, NULL);

    If something within linux_nat_resume_callback throws, GDB leaves the
    lwp_info as if the inferior was resumed, while it actually wasn't.

    A couple examples, there are possibly others:

     - i386_linux_resume calls target_read which calls QUIT.
     - if the actual ptrace resumption fails in inf_ptrace_resume,
       perror_with_name is called.

    If the user tries to kill the inferior at this point (or quit, which
    offers to kill), GDB locks up trying to stop the lwp -- if it is
    already stopped no new waitpid event gets generated for it.

    Fix this by setting the stopped flag earlier, as soon as we collect a
    stop event with waitpid, and clearing it always only after resuming
    the lwp successfully.

    Tested on x86_64 Fedora 20.  Confirmed the lock-up disappears using a
    local hack that forces an error in inf_ptrace_resume.

    Also fixes a little "set debug lin-lwp" annoyance.  Currently we always
see:

     Continuing.
     LLR: Preparing to resume process 6802, 0, inferior_ptid Thread
0x7ffff7fc7740 (LWP 6802)

    ^^^^^^^^
     RC: Resuming sibling Thread 0x7ffff77c5700 (LWP 6807), 0, resume
     RC: Resuming sibling Thread 0x7ffff7fc6700 (LWP 6806), 0, resume
     RC: Not resuming sibling Thread 0x7ffff7fc7740 (LWP 6802) (not stopped)
                                                     ^^^^^^^^^^^^^^^^^^^^^^^
     LLR: PTRACE_CONT process 6802, 0 (resume event thread)

    This patch gets rid of the "Not resuming sibling" line.

    2014-05-29  Pedro Alves  <palves@redhat.com>

        PR gdb/15713
        * linux-nat.c (linux_nat_resume_callback): Rename the second
        parameter to 'except'.  Skip LP if it points to EXCEPT.
        (linux_nat_resume): Don't mark the event lwp as not stopped
        before resuming sibling lwps.  Instead ask
        linux_nat_resume_callback to skip the event lwp.  Mark it as not
        stopped after actually resuming it.
        (linux_handle_syscall_trap): Mark the lwp as not stopped after
        resuming it.
        (wait_lwp): Mark the lwp as stopped here.
        (stop_wait_callback): Mark the lwp as not stopped right after
        resuming it.  Don't mark lwps as stopped here.
        (linux_nat_filter_event): Mark the lwp as stopped earlier.
        (linux_nat_wait_1): Don't mark dead lwps as stopped here.

-----------------------------------------------------------------------

Summary of changes:
 gdb/ChangeLog   |   17 +++++++++++++++++
 gdb/linux-nat.c |   41 ++++++++++++++++++-----------------------
 2 files changed, 35 insertions(+), 23 deletions(-)

--
You are receiving this mail because:
You are on the CC list for the bug.

[Bug win32/10004] gdb cannot continue after SIGFPE or SIGSEGV happen on windows

[schwab at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=10004

Andreas Schwab <schwab at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|jackie.rosen at hushmail dot com   |

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug win32/10004] gdb cannot continue after SIGFPE or SIGSEGV happen on windows

[jackie.rosen at hushmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=10004

Jackie Rosen <jackie.rosen at hushmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jackie.rosen at hushmail dot com

--- Comment #5 from Jackie Rosen <jackie.rosen at hushmail dot com> ---
*** Bug 260998 has been marked as a duplicate of this bug. ***
Seen from the domain http://volichat.com
Page where seen: http://volichat.com/adult-chat-rooms
Marked for reference. Resolved as fixed @bugzilla.

-- 
You are receiving this mail because:
You are on the CC list for the bug.