Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: RAJESH DASARI <raajeshdasari@gmail.com>
To: gdb@sourceware.org
Subject: Reg : gdb crash is seen while attaching a process to gdb.
Date: Fri, 24 Mar 2017 06:27:00 -0000	[thread overview]
Message-ID: <CAPXMrf8TH66vZtp+9riDpDR4fBizip5-LQtZ9+1nSfVaywTLxg@mail.gmail.com> (raw)

Hi ,

I am experiencing a gdb crash when i am trying to attach and dettach a
process(this process is a multi threaded application) to gdb on my
mips64 based linux environment.

ps -L -p 7889 | wc -l
15


# gdb -p 7889
GNU gdb (GDB) 7.12.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "mips64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 7889
[New LWP 7895]
[New LWP 7896]
Couldn't write debug register: No such process.
(gdb) quit
A debugging session is active.

    Inferior 1 [process 7889] will be detached.

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.



Thanks,
Rajesh Dasari.


             reply	other threads:[~2017-03-24  6:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24  6:27 RAJESH DASARI [this message]
2017-03-24 11:32 ` Yao Qi
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=CAPXMrf8TH66vZtp+9riDpDR4fBizip5-LQtZ9+1nSfVaywTLxg@mail.gmail.com \
    --to=raajeshdasari@gmail.com \
    --cc=gdb@sourceware.org \
    /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