From: Pedro Alves <pedro@palves.net>
To: Simon Marchi <simon.marchi@efficios.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: make "start" breakpoint inferior-specific
Date: Tue, 8 Nov 2022 21:09:21 +0000 [thread overview]
Message-ID: <691c5a58-68ae-5fe9-2f3d-34fb7af69ad0@palves.net> (raw)
In-Reply-To: <b881b3db-fb81-b4fa-cff0-208f1584f85f@efficios.com>
On 2022-11-08 8:14 p.m., Simon Marchi wrote:
> Ok, I think I found an alternative solution for the test, to make the
> inferiors sleep a bit before main. I can achieve that in a C program
> using __attribute__((constructor)), but I believe that's a GCC
> extension? Otherwise, I can do it in C++ using the constructor of a
> global object. Which one would be best? Or, do you see another way?
A C++ global object sounds best.
next prev parent reply other threads:[~2022-11-08 21:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 17:40 Simon Marchi
2022-08-17 17:56 ` Simon Marchi
2022-08-31 14:03 ` Bruno Larsen
2022-11-04 16:52 ` Simon Marchi
2022-11-07 8:14 ` Bruno Larsen
2022-11-08 17:24 ` Tom Tromey
2022-09-01 10:42 ` Andrew Burgess
2022-11-04 17:24 ` Simon Marchi
[not found] ` <8735asb7cj.fsf@redhat.com>
2022-11-09 13:19 ` Simon Marchi
2022-11-08 19:43 ` Pedro Alves
2022-11-08 20:14 ` Simon Marchi
2022-11-08 21:09 ` Pedro Alves [this message]
2022-11-08 21:20 ` [PATCH v2] " Simon Marchi
2022-11-10 16:45 ` Pedro Alves
2022-11-10 17:33 ` Simon Marchi
2022-11-10 17:36 ` Simon Marchi
2022-11-10 17:47 ` Pedro Alves
2022-11-10 17:53 ` Simon Marchi
2022-11-11 12:37 ` Tom de Vries
2022-11-11 13:53 ` Simon Marchi
2022-11-11 15:21 ` Tom de Vries
2022-11-11 19:03 ` Simon Marchi
2022-11-12 10:43 ` Tom de Vries
2022-11-14 11:29 ` Tom de Vries
2022-11-14 13:19 ` Simon Marchi
2022-11-14 14:18 ` Tom de Vries
2022-11-16 16:22 ` Tom Tromey
2022-11-16 16:26 ` Simon Marchi
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=691c5a58-68ae-5fe9-2f3d-34fb7af69ad0@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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).