From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 95142 invoked by alias); 31 Jul 2015 11:18:47 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org Received: (qmail 95118 invoked by uid 48); 31 Jul 2015 11:18:47 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/18749] New: problems if whole process dies while (ptrace-) stopped Date: Fri, 31 Jul 2015 11:18:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: 2015-q3/txt/msg00134.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=18749 Bug ID: 18749 Summary: problems if whole process dies while (ptrace-) stopped Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: palves at redhat dot com Target Milestone: --- Between fetching a thread stop event (on Linux, after waitpid returns a stop) and fully handling the event (e.g., all the way evaluating a breakpoint condition and reresuming if it evals false), some other thread that is still running may cause the whole process to exit. Usually in such a situation, the lower level code that tries to access memory or registers throws an error (usually a perror_with_name/ESRCH), and many code paths in GDB don't expect this, resulting in a broken debug session. -- You are receiving this mail because: You are on the CC list for the bug.