From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Tom Tromey <tom@tromey.com>
Cc: Pedro Alves via Gdb-patches <gdb-patches@sourceware.org>,
Pedro Alves <palves@redhat.com>
Subject: Re: Unbreaking gdb on Solaris post-multitarget [PR 25939]
Date: Wed, 17 Jun 2020 19:07:11 +0200 [thread overview]
Message-ID: <yddo8phbozk.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <87wo45d7g3.fsf@tromey.com> (Tom Tromey's message of "Wed, 17 Jun 2020 09:43:08 -0600")
Hi Tom,
> Pedro> Could this be a race somehow more exposed now due to GDB now
> Pedro> spawning worker
> Pedro> threads? What happens if you debug a GDB that doesn't spawn worker
> Pedro> threads? Like:
>
> Pedro> ./gdb -D ./data-directory --args ./gdb -ex "maint set worker-threads 0"
>
> You have to be sure to build without Guile if you want to try this; the
> garbage collector automatically starts threads as well.
thanks for the hint. Fortunately, Guile is no longer bundled with
Solaris 11.4 and the libguile I had built some time ago for autogen is
32-bit only.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
prev parent reply other threads:[~2020-06-17 17:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 14:21 Rainer Orth
2020-06-16 19:16 ` Pedro Alves
2020-06-17 14:45 ` Rainer Orth
2020-06-18 14:55 ` Pedro Alves
2020-06-18 15:51 ` Pedro Alves
2020-06-19 12:36 ` Rainer Orth
2020-06-19 13:55 ` Pedro Alves
2020-06-21 16:37 ` [COMMITTED PATCH][PR gdb/25939] Move push_target call earlier in procfs.c Rainer Orth
2020-06-22 10:19 ` Pedro Alves
2020-06-17 15:43 ` Unbreaking gdb on Solaris post-multitarget [PR 25939] Tom Tromey
2020-06-17 17:07 ` Rainer Orth [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=yddo8phbozk.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).