public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Fix fork-related regressions on GNU/Linux
Date: Thu, 05 Oct 2017 17:35:00 -0000	[thread overview]
Message-ID: <2fd9d7ca17539ce983862b25e0abc27cfb706189@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 2fd9d7ca17539ce983862b25e0abc27cfb706189 ***

Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 2fd9d7ca17539ce983862b25e0abc27cfb706189

Fix fork-related regressions on GNU/Linux

Commit 5cd63fda035d ("Fix "Remote 'g' packet reply is too long"
problems with multiple inferiors") caused a number of regressions on
native GNU/Linux, all related to follow-fork support.  E.g.:

  src/gdb/target.c:3141: internal-error: gdbarch* default_thread_architecture(target_ops*, ptid_t): Assertion `inf != NULL' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n)
  Resyncing due to internal error.
  FAIL: gdb.base/catch-signal-fork.exp: got SIGHUP after fork (GDB internal error)

This commit fixes it.

gdb/ChangeLog:
2017-10-05  Pedro Alves  <palves@redhat.com>

	* linux-nat.c (linux_child_follow_fork): When following the parent
	and detaching the child, consult the parent thread's architecture
	instead of the child's.


             reply	other threads:[~2017-10-05 17:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-05 17:35 sergiodj+buildbot [this message]
2017-10-05 17:58 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2017-10-05 21:12 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot
2017-10-05 23:32 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2017-10-06  0:01 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-10-06  1:56 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-10-06  2:21 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-10-18 13:04 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2017-10-18 19:39 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2017-10-19  2:14 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-10-19  3:47 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2017-10-22  6:53 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2017-10-22 16:06 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot
2017-10-22 17:40 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
2017-10-23  2:54 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot

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=2fd9d7ca17539ce983862b25e0abc27cfb706189@gdb-build \
    --to=sergiodj+buildbot@sergiodj.net \
    --cc=gdb-testers@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).