Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: RAJESH DASARI <raajeshdasari@gmail.com>
Cc: GDB <gdb@sourceware.org>
Subject: Re: Reg : gdb crash is seen while attaching a process to gdb.
Date: Fri, 24 Mar 2017 11:32:00 -0000	[thread overview]
Message-ID: <CAH=s-PPcmOkY-yPuGsDbE0L=Q=SC9qjw9afTZnHfRE_oMPTzVA@mail.gmail.com> (raw)
In-Reply-To: <CAPXMrf8TH66vZtp+9riDpDR4fBizip5-LQtZ9+1nSfVaywTLxg@mail.gmail.com>

On Fri, Mar 24, 2017 at 6:27 AM, RAJESH DASARI <raajeshdasari@gmail.com> wrote:
>
> 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
>
> This is a bug, please report it.  For instructions, see:
> <http://www.gnu.org/software/gdb/bugs/>.
>
> 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)
>
>
> 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.
>
>

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.

-- 
Yao (齐尧)


  reply	other threads:[~2017-03-24 11:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24  6:27 RAJESH DASARI
2017-03-24 11:32 ` Yao Qi [this message]
2017-03-25 12:49   ` RAJESH DASARI
2017-03-27  8:54     ` Yao Qi
     [not found]       ` <CAPXMrf9sjaQ4DUF+2guOYNE2FGRsM7RCcnRxZZ6VT28xLu40ZA@mail.gmail.com>
2017-04-27  6:13         ` RAJESH DASARI
2017-04-27  9:16           ` Andreas Schwab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH=s-PPcmOkY-yPuGsDbE0L=Q=SC9qjw9afTZnHfRE_oMPTzVA@mail.gmail.com' \
    --to=qiyaoltc@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=raajeshdasari@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox