public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/18717] gdb misbehaves if non-leader thread exits process
Date: Fri, 24 Jul 2015 17:29:00 -0000	[thread overview]
Message-ID: <bug-18717-4717-BwibdsRX2a@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18717-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Pedro Alves <palves@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7759842763d94dc2f1c7d52d09f9203830b753ab

commit 7759842763d94dc2f1c7d52d09f9203830b753ab
Author: Pedro Alves <palves@redhat.com>
Date:   Fri Jul 24 18:18:44 2015 +0000

    PR gdb/18717: internal error if non-leader thread exits process

    If a non-leader thread exits the process while all other threads are
    ptrace-stopped, native gdb fails an assertion.  The test added by this
    commit catches it:

     /home/pedro/gdb/mygit/build/../src/gdb/linux-nat.c:3198: internal-error:
linux_nat_filter_event: Assertion `lp->resumed' failed.
     A problem internal to GDB has been detected,
     further debugging may prove unreliable.
     Quit this debugging session? (y or n)
     FAIL: gdb.threads/non-leader-exit-process.exp: program exits normally (GDB
internal error)

    The fix is just to remove the assertion.

    With that out of the way, neither GDB not GDBserver handle this
    perfectly though, so I'm adding a KFAIL:

     (gdb) continue
     Continuing.
     [Thread 0x7ffff7fc0700 (LWP 15350) exited]
     No unwaited-for children left.
     Couldn't get registers: No such process.
     (gdb) KFAIL: gdb.threads/non-ldr-exit.exp: program exits normally (PRMS:
gdb/18717)

    gdb/ChangeLog:
    2015-07-24  Pedro Alves  <palves@redhat.com>

        PR gdb/18717
        * linux-nat.c (linux_nat_filter_event): Don't assert that the lwp
        is resumed, and extend the debug log.

    gdb/testsuite/ChangeLog:
    2015-07-24  Pedro Alves  <palves@redhat.com>

        PR gdb/18717
        * gdb.threads/non-ldr-exit.c: New file.
        * gdb.threads/non-ldr-exit.exp: New file.

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


      parent reply	other threads:[~2015-07-24 17:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-24 17:18 [Bug gdb/18717] New: " palves at redhat dot com
2015-07-24 17:18 ` [Bug gdb/18717] " palves at redhat dot com
2015-07-24 17:29 ` cvs-commit at gcc dot gnu.org [this message]

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=bug-18717-4717-BwibdsRX2a@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).