From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 100538 invoked by alias); 25 Mar 2017 12:49:20 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 100513 invoked by uid 89); 25 Mar 2017 12:49:18 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:1449, H*x:iPhone, H*UA:iPhone, management X-HELO: mail-pg0-f41.google.com Received: from mail-pg0-f41.google.com (HELO mail-pg0-f41.google.com) (74.125.83.41) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 25 Mar 2017 12:49:17 +0000 Received: by mail-pg0-f41.google.com with SMTP id 21so7842852pgg.1 for ; Sat, 25 Mar 2017 05:49:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=CrzOTrRX/Te60o59tZh+i+NxjFCvUyuud55F5zfseaE=; b=FlMqNmUe8xR22HTDH+ZwXI84SnSvEMdhFOqEG7CoW29LXDj3Tit9FCL8oZLlGdMquH UNgEAHs5Vnf9InVNpgUnKhwy92z1Th4Y+GkUHMFcdKf4j4ZAXCnl3A5RBTD8CQPCrNws VLJYPaOW4t69mvzc34lbCVp612R7VTPAZw14HZ4CmqT+Oy90vbYtXq/aj+DJBFOJM67X u+fMJ0uspkhdZVWN7lIqvmuDY0Q/46I4qPfNPnwIedWzgBHM8oY5dTBerqehQVAruiMg oeBWLACKrp9Aozk0y8lalZeAOLyEmHgOxOmgeVXoUyLN5IkinJf2wcksiFn+DZWj/7ex RRUw== X-Gm-Message-State: AFeK/H28CT0rz1DjoSvJHC3e6td3SRdBRe04myv579oqFD9O2NW62T+TQYrG6Px4KmDmDw== X-Received: by 10.98.15.145 with SMTP id 17mr14482598pfp.183.1490446156860; Sat, 25 Mar 2017 05:49:16 -0700 (PDT) Received: from [100.105.71.117] ([223.186.147.117]) by smtp.gmail.com with ESMTPSA id s13sm10552704pfd.46.2017.03.25.05.49.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 25 Mar 2017 05:49:15 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: Reg : gdb crash is seen while attaching a process to gdb. From: RAJESH DASARI In-Reply-To: Date: Sat, 25 Mar 2017 12:49:00 -0000 Cc: GDB Content-Transfer-Encoding: quoted-printable Message-Id: <728178DD-B9FD-4695-A7FF-F13B829DFD2E@gmail.com> References: To: Yao Qi X-SW-Source: 2017-03/txt/msg00058.txt.bz2 Thanks for your quick response . Could you please share those patches , I w= ill recompile the gdb with the patches and test the changes. Regards, Rajesh. > On 24-Mar-2017, at 17:02, Yao Qi wrote: >=20 >> On Fri, Mar 24, 2017 at 6:27 AM, RAJESH DASARI = wrote: >>=20 >> Quit anyway? (y or n) y >> gdb-7.12.1/gdb/thread.c:1010: internal-error: int >> is_executing(ptid_t): Assertion `tp' failed. >> A problem internal to GDB has been detected, >> further debugging may prove unreliable. >> Quit this debugging session? (y or n) y >>=20 >> This is a bug, please report it. For instructions, see: >> . >>=20 >> gdb-7.12.1/gdb/thread.c:1010: internal-error: int >> is_executing(ptid_t): Assertion `tp' failed. >> A problem internal to GDB has been detected, >> further debugging may prove unreliable. >> Create a core file of GDB? (y or n) y >> Aborted (core dumped) >>=20 >>=20 >> I notice this problem only for some processes, there are few more >> multi-threaded processes which are not showing this problem. Could you >> please share some pointers on what could be causing this gdb crash. >>=20 >>=20 >=20 > I suspect it is related to the improper management of thread_info's > refcount. I've already had some patches in my local tree, but don't > have time posting them. Let me find them, and polish them. >=20 > --=20 > Yao (=E9=BD=90=E5=B0=A7)