From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-17517-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 6939 invoked by alias); 20 Feb 2015 18:20:34 -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
Received: (qmail 6915 invoked by uid 48); 20 Feb 2015 18:20:33 -0000
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/18006] New: internal error if threaded program calls
 clone(CLONE_VM)
Date: Fri, 20 Feb 2015 18:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: threads
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-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
Message-ID: <bug-18006-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: 2015-q1/txt/msg00282.txt.bz2

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

            Bug ID: 18006
           Summary: internal error if threaded program calls
                    clone(CLONE_VM)
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: threads
          Assignee: unassigned at sourceware dot org
          Reporter: palves at redhat dot com

On GNU/Linux, if a pthreaded program has a thread call clone(CLONE_VM)
directly,
and then that clone LWP hits a debug event (breakpoint, etc.) GDB internal
errors.  Threaded programs shouldn't really be calling clone directly, but GDB
shouldn't crash either.

On GDB 7.9, the crash looks like:

 (gdb) break clone_fn
 Breakpoint 2 at 0x4007d8: file clone-thread_db.c, line 35.
 (gdb) r
 ...
 [Thread debugging using libthread_db enabled]
 ...
 /home/pedro/gdb/mygit/src/gdb/linux-nat.c:1030: internal-error:
lin_lwp_attach_lwp: Assertion `lwpid > 0' failed.
 A problem internal to GDB has been detected,
 further debugging may prove unreliable.

On earlier releases, it looked like this:

 (gdb) b clone_fn 
 Breakpoint 1 at 0x4007d8: file clone-thread_db.c, line 35.
 (gdb) r
 ...
 [Thread debugging using libthread_db enabled]
 ...
 [New Thread 0x7ffff7fc2700 (LWP 3886)]
 ../../gdb/linux-thread-db.c:437: internal-error: thread_get_info_callback:
Assertion `inout->thread_info != NULL' failed.
 A problem internal to GDB has been detected,
 further debugging may prove unreliable.

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